Skip to main content
Meta Stack Exchange

Return to Answer

Second iteration.
Source Link
This_is_NOT_a_forum
This_is_NOT_a_forum
  • 6.7k
  • 4
  • 37
  • 55

A bit of a crosspost -

A recent change in the 'design' of Cascadia Code mono has rendered italic fonts to look cursive. When composing a post - the text area is in monospace. Specifically - when composing a post in the teams or "alpha" editor - using italics will result in text looking like this:

Enter image description here

The font used for monospace italics on TeamsTeams (when composing a post in Markdown mode) are a little hard to read. It might be my dyslexia but, the r, f,l and s are... indistinct and significantly harder to read than the fonts used elsewhere. I'm *reasonably* certain, as someone who abuses italics for effect that this change happened *after* an update on the *OS* end - which might be an issue with using a font that seems to be in development, and I suspect an unintended, and unexpected change.

Regular Monospace looks fine:

Enter image description here

Interestingly, the 'regular' editor doesn't have this issue since it doesn't show styles inline. It also apparently affects italic monospace in comments.

I'm on Windows 10 (build 19043), and am running Vivaldi 3.8 (while unsupported, it's another Blink/Chrome-based browser). I suspect, but I am unsure if the May "Feature update to Windows 10, version 21H1" might have triggered this change.

A bit of a crosspost -

A recent change in the 'design' of Cascadia Code mono has rendered italic fonts to look cursive. When composing a post - the text area is in monospace. Specifically - when composing a post in the teams or "alpha" editor - using italics will result in text looking like this

Enter image description here

The font used for monospace italics on Teams (when composing a post in Markdown mode) are a little hard to read. It might be my dyslexia but, the r, f,l and s are... indistinct and significantly harder to read than the fonts used elsewhere. I'm *reasonably* certain, as someone who abuses italics for effect that this change happened *after* an update on the *OS* end - which might be an issue with using a font that seems to be in development, and I suspect an unintended, and unexpected change.

Regular Monospace looks fine:

Enter image description here

Interestingly, the 'regular' editor doesn't have this issue since it doesn't show styles inline. It also apparently affects italic monospace in comments

I'm on Windows 10 (build 19043), and running Vivaldi 3.8 (while unsupported, it's another Blink/Chrome-based browser). I suspect, but am unsure if the May "Feature update to Windows 10, version 21H1" might have triggered this change

A bit of a crosspost -

A recent change in the 'design' of Cascadia Code mono has rendered italic fonts to look cursive. When composing a post - the text area is in monospace. Specifically - when composing a post in the teams or "alpha" editor - using italics will result in text looking like this:

Enter image description here

The font used for monospace italics on Teams (when composing a post in Markdown mode) are a little hard to read. It might be my dyslexia but, the r, f,l and s are... indistinct and significantly harder to read than the fonts used elsewhere. I'm *reasonably* certain, as someone who abuses italics for effect that this change happened *after* an update on the *OS* end - which might be an issue with using a font that seems to be in development, and I suspect an unintended, and unexpected change.

Regular Monospace looks fine:

Enter image description here

Interestingly, the 'regular' editor doesn't have this issue since it doesn't show styles inline. It also apparently affects italic monospace in comments.

I'm on Windows 10 (build 19043) and am running Vivaldi 3.8 (while unsupported, it's another Blink/Chrome-based browser). I suspect, but I am unsure if the May "Feature update to Windows 10, version 21H1" might have triggered this change.

Active reading [<https://en.wikipedia.org/wiki/Cascadia_Code> <https://en.wikipedia.org/wiki/Markdown> <https://en.wikipedia.org/wiki/Windows_10> <https://en.wikipedia.org/wiki/Vivaldi_%28web_browser%29> <https://en.wikipedia.org/wiki/Google_Chrome>].
Source Link
This_is_NOT_a_forum
This_is_NOT_a_forum
  • 6.7k
  • 4
  • 37
  • 55

BitA bit of a crossposta crosspost -

A recent change in the 'design' of cascadiaCascadia Code mono has rendered italic fonts to look cursive. When composing a post - the text area is in monospace. Specifically - when composing a post in the teams or "alpha" editor - using italics will result in text looking like this

enter image description hereEnter image description here

The font used for monospace italics on teamsTeams (when composing a post in markdownMarkdown mode) are a little hard to read. It might be my dyslexia but, the r, f,l and s are... indistinct and significantly harder to read than the fonts used elsewhere. I'm *reasonably* certain, as someone who abuses italics for effect that this change happened *after* an update on the *OS* end - which might be an issue with using a font that seems to be in development, and I suspect an unintended, and unexpected change.

Regular Monospace looks fine:

enter image description hereEnter image description here

Interestingly, the 'regular' editor doesn't have this issue since it doesn't show styles inline. It also apparently affects italic monospace in comments

I'm on windows 10Windows 10 ( Buildbuild 19043), and running vivaldiVivaldi 3.8 (while unsupported, itsit's another blinkBlink/chrome basedChrome-based browser). I suspect, but am unsure if the May "Feature update to Windows 10, version 21H1" might have triggered this change

Bit of a crosspost -

A recent change in the 'design' of cascadia mono has rendered italic fonts to look cursive. When composing a post - the text area is in monospace. Specifically - when composing a post in the teams or "alpha" editor - using italics will result in text looking like this

enter image description here

The font used for monospace italics on teams (when composing a post in markdown mode) are a little hard to read. It might be my dyslexia but, the r, f,l and s are... indistinct and significantly harder to read than the fonts used elsewhere. I'm *reasonably* certain, as someone who abuses italics for effect that this change happened *after* an update on the *OS* end - which might be an issue with using a font that seems to be in development, and I suspect an unintended, and unexpected change

Regular Monospace looks fine

enter image description here

Interestingly, the 'regular' editor doesn't have this issue since it doesn't show styles inline. It also apparently affects italic monospace in comments

I'm on windows 10 ( Build 19043), and running vivaldi 3.8 (while unsupported, its another blink/chrome based browser). I suspect, but am unsure if the May "Feature update to Windows 10, version 21H1" might have triggered this change

A bit of a crosspost -

A recent change in the 'design' of Cascadia Code mono has rendered italic fonts to look cursive. When composing a post - the text area is in monospace. Specifically - when composing a post in the teams or "alpha" editor - using italics will result in text looking like this

Enter image description here

The font used for monospace italics on Teams (when composing a post in Markdown mode) are a little hard to read. It might be my dyslexia but, the r, f,l and s are... indistinct and significantly harder to read than the fonts used elsewhere. I'm *reasonably* certain, as someone who abuses italics for effect that this change happened *after* an update on the *OS* end - which might be an issue with using a font that seems to be in development, and I suspect an unintended, and unexpected change.

Regular Monospace looks fine:

Enter image description here

Interestingly, the 'regular' editor doesn't have this issue since it doesn't show styles inline. It also apparently affects italic monospace in comments

I'm on Windows 10 (build 19043), and running Vivaldi 3.8 (while unsupported, it's another Blink/Chrome-based browser). I suspect, but am unsure if the May "Feature update to Windows 10, version 21H1" might have triggered this change

added 60 characters in body
Source Link
Journeyman Geek Mod
Journeyman Geek Mod
  • 192.8k
  • 50
  • 362
  • 768

Bit of a crosspost -

A recent change in the 'design' of cascadia mono has rendered italic fonts to look cursive. When composing a post - the text area is in monospace. Specifically - when composing a post in the teams or "alpha" editor - using italics will result in text looking like this

enter image description here

The font used for monospace italics on teams (when composing a post in markdown mode) are a little hard to read. It might be my dyslexia but, the r, f,l and s are... indistinct and significantly harder to read than the fonts used elsewhere. I'm *reasonably* certain, as someone who abuses italics for effect that this change happened *after* an update on the *OS* end - which might be an issue with using a font that seems to be in development, and I suspect an unintended, and unexpected change

Regular Monospace looks fine

enter image description here

Interestingly, the 'regular' editor doesn't have this issue since it doesn't show styles inline. It also apparently affects italic monospace in comments

I'm on windows 10 ( Build 19043), and running vivaldi 3.8 (while unsupported, its another blink/chrome based browser). I suspect, but am unsure if the May "Feature update to Windows 10, version 21H1" might have triggered this change

Bit of a crosspost -

A recent change in the 'design' of cascadia mono has rendered italic fonts to look cursive. When composing a post - the text area is in monospace. Specifically - when composing a post in the teams or "alpha" editor - using italics will result in text looking like this

enter image description here

The font used for monospace italics on teams (when composing a post in markdown mode) are a little hard to read. It might be my dyslexia but, the r, f,l and s are... indistinct and significantly harder to read than the fonts used elsewhere. I'm *reasonably* certain, as someone who abuses italics for effect that this change happened *after* an update on the *OS* end - which might be an issue with using a font that seems to be in development, and I suspect an unintended, and unexpected change

Regular Monospace looks fine

enter image description here

Interestingly, the 'regular' editor doesn't have this issue since it doesn't show styles inline.

I'm on windows 10 ( Build 19043), and running vivaldi 3.8 (while unsupported, its another blink/chrome based browser). I suspect, but am unsure if the May "Feature update to Windows 10, version 21H1" might have triggered this change

Bit of a crosspost -

A recent change in the 'design' of cascadia mono has rendered italic fonts to look cursive. When composing a post - the text area is in monospace. Specifically - when composing a post in the teams or "alpha" editor - using italics will result in text looking like this

enter image description here

The font used for monospace italics on teams (when composing a post in markdown mode) are a little hard to read. It might be my dyslexia but, the r, f,l and s are... indistinct and significantly harder to read than the fonts used elsewhere. I'm *reasonably* certain, as someone who abuses italics for effect that this change happened *after* an update on the *OS* end - which might be an issue with using a font that seems to be in development, and I suspect an unintended, and unexpected change

Regular Monospace looks fine

enter image description here

Interestingly, the 'regular' editor doesn't have this issue since it doesn't show styles inline. It also apparently affects italic monospace in comments

I'm on windows 10 ( Build 19043), and running vivaldi 3.8 (while unsupported, its another blink/chrome based browser). I suspect, but am unsure if the May "Feature update to Windows 10, version 21H1" might have triggered this change

added 126 characters in body
Source Link
Journeyman Geek Mod
Journeyman Geek Mod
  • 192.8k
  • 50
  • 362
  • 768
Source Link
Journeyman Geek Mod
Journeyman Geek Mod
  • 192.8k
  • 50
  • 362
  • 768