You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Select a braille table that can report italic text.
From Preferences --> Document formatting, uncheck Font attributes.
Read the following line (tested with Firefox 55).
This is italic text.
Expected behavior:
The italic text is not marked as italic.
Actual behavior:
Speech does indeed not mention the italic attribute, but braille still shows it.
Other information
Can't reproduce in Word, so it seems specific to browse mode.
First reported by @rimas-kudelis in #1885 (comment). The key take-away point is that this problem is quite annoying for users on the web, and if unresolved may lead to people "fixing" braille tables to exclude bold/italic/etc altogether.
The text was updated successfully, but these errors were encountered:
LeonarddeR
changed the title
Document formatting preferences don't always apply to braille in borwse mode
Document formatting preferences don't always apply to braille in browse mode
Sep 20, 2017
This can be fixed with a simple patch of braille.py to consider formatConfig before sending text formatting flags to liblouis.
A further optimization is to not fetch IA2 text attributes and object attributes if all the formatConfig options that rely on them are disabled. This saves a few COM calls but the gains are probably minimal.
Steps to reproduce:
This is italic text.
Expected behavior:
The italic text is not marked as italic.
Actual behavior:
Speech does indeed not mention the italic attribute, but braille still shows it.
Other information
Can't reproduce in Word, so it seems specific to browse mode.
First reported by @rimas-kudelis in #1885 (comment). The key take-away point is that this problem is quite annoying for users on the web, and if unresolved may lead to people "fixing" braille tables to exclude bold/italic/etc altogether.
The text was updated successfully, but these errors were encountered: