[prev in list] [next in list] [prev in thread] [next in thread] 

List:       trac
Subject:    [Trac] Idea for #371: Navbar layout improperly in Opera
From:       cmlenz () gmx ! de (Christopher Lenz)
Date:       2004-12-20 5:53:54
Message-ID: 6E98549E-5275-11D9-9198-000A95B24066 () gmx ! de
[Download RAW message or body]

Am 02.12.2004 um 17:48 schrieb Christopher Lenz:
> Am 02.12.2004 um 17:33 schrieb Tom Clancy:
>>> I propose to insert this code into header.cs after the mainnav . . .
>> Any opposition on this approach?
>>
>> Not to your suggestion so much as the current implementation
>> direction. I haven't spent a lot of time looking at Trac's HTML or
>> CSS, but this is stuff I can actually give something back on. Why use
>> JavaScript to influence CSS except as a last approach? There are a
>> number of ways to hack around most browsers within CSS
>> (http://centricle.com/ref/css/filters/ is usually my first stop though
>> Opera 7 isn't listed). That saves worrying about people disabling JS
>> and it keeps a better separation of presentation and content.
>
> If I had been able to find a CSS filter for Opera 7, this problem 
> would have been worked around ages ago :-P

Finally, I've been able to find a solution for the navbar that works 
nicely in all browsers I have available for testing. This change will 
be included in 0.8.1 unless someone finds a regression. Testing would 
be welcome. See changesets 
http://projects.edgewall.com/trac/changeset/1129 (for trunk) and 
http://projects.edgewall.com/trac/changeset/1131 (for the 0.8 branch).

Cheers, Chris
--
Christopher Lenz
/=/ cmlenz at gmx.de

[prev in list] [next in list] [prev in thread] [next in thread]