Bug 45401 - Authoring-GUI css bugs in Firefox 3
Summary: Authoring-GUI css bugs in Firefox 3
Status: NEW
Alias: None
Product: Lenya
Classification: Unclassified
Component: Miscellaneous (show other bugs)
Version: Trunk
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Lenya Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-15 11:38 UTC by Juergen Ragaller
Modified: 2008-08-25 05:59 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Juergen Ragaller 2008-07-15 11:38:01 UTC
The lenya authoring gui has the following GUI bugs in Firefox 3:

- Reload of area tabs: When a reload of an area is done (mouse or key) the area tab moves down (by ca. 2-4px). This occurs always on the authoring tab and sometimes on the site and admin tab (non deterministic bug type ;-))

- Font size of site tree widget: In some cases the font size of the entries in the site tree widget is not 11px (as written in css) but much bigger. This occurs randomly...


Observation regarding CSS: In the authoring area the page.css has an influence on the looks of the table, wich IMO is bad. The rules in menu.css should describe all commonly used properties for the xhtml elements used in the tabs - even if the default is fine - in order not to be easily overwritable by a rule in a websites css.


WDYT?
Comment 1 Andreas Hartmann 2008-08-25 05:59:53 UTC
(In reply to comment #0)

> - Font size of site tree widget: In some cases the font size of the entries in
> the site tree widget is not 11px (as written in css) but much bigger. This
> occurs randomly...

I think I have fixed this one, please test - TIA!

> Observation regarding CSS: In the authoring area the page.css has an influence
> on the looks of the table, wich IMO is bad. The rules in menu.css should
> describe all commonly used properties for the xhtml elements used in the tabs -
> even if the default is fine - in order not to be easily overwritable by a rule
> in a websites css.

That sounds reasonable, but wouldn't the CSS become very large?