Acquisitions (and other Dojo-based interfaces) generally don't respect global font settings
Bug #996026 reported by
Lebbeous Fogle-Weekley
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
To quote Sharon Herbert of Sitka:
---
No part of the Acquisitions Module follows the global font settings. Some staff depend on the ability
to increase the font size in Evergreen.
---
I talked to Jason Etheridge about this in IRC. He believes he sees a straightforward approach to correcting this in Acquisitions and other similary-
Changed in evergreen: | |
status: | New → Confirmed |
Changed in evergreen: | |
status: | Confirmed → Won't Fix |
To post a comment you must log in.
Here's the bird's eye view of how the font settings work now in the XUL interfaces:
1) global.css file gets loaded by every interface
It contains lines like this:
.ALL_FONTS_SMALLER * { font-size-adjust: .3 !important;}
.ALL_FONTS_SMALLER *|* { font-size-adjust: .3 !important;}
which affect any elements and descendants with the corresponding classname.
2) during the onload event interfaces will call font_helper()
This looks at the desired font settings (stored with OpenILS/data.js) and sets classnames like ALL_FONTS_SMALLER on document. documentElement , triggering the CSS.
So, for non-XUL interfaces that get embedded in the staff client, we could either have them do something similar, or, if they're wrapped in a XUL <browser/> powered by util/browser.js, we could try to have browser.js do the work and inject CSS and CSS classnames into the embedded page with every page load. That might work.