#10031 closed defect (bug) (wontfix)
Rendering problem with larr/rarr entities
| Reported by: | Denis-de-Bernardy | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Administration | Version: | 2.8 |
| Severity: | minor | Keywords: | |
| Cc: | Focuses: |
Description
Related to this bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=439118
We should probably switch back to using laquo/raquo.
Change History (4)
#2
@
17 years ago
- Cc added
It's a font rendering bug. IE8 has a couple as well (cannot render some glyphs in certain fonts. • is one that comes to mind).
The problem with using laquo/raquo is that these are quotation marks, telling screen reader users that the content inside is a quotation. They get read « as "left double angle quote" and » as "right double angle quote" (some assistive devices even spit out "left-pointing double angle quotation mark") which is a whole lot of mess when they are incorrectly used to create a pretty visual display.
Far better (IMO) to leave WP alone and hope the browser bugs are sorted quickly.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
affects MacOS only, so can wait until 2.9