Gunlaug Sørtun wrote:
> Alan Gresley wrote:
>
>> If this is this bug
>
>> <http://css-class.com/test/css/visformatting/floats/floats-width-auto.htm>
>>
>
> Although dealing with vertical alignment of floats, our test case isn't
> revealing just one bug.
>
> Reordering the markup is the old solution, and it'll still work -
> if that's an option.
>
> Another option is to absolute position relevant elements, thus avoid old
> float-alignment bugs altogether.
>
>
> To return to what appears to be the original poster's case:
> <http://test3.dekkers.net/login.htm>
> ...a fix for older Geckos will make it appear like this...
> Page: <http://www.gunlaug.no/tos/alien/id/test_09_0502.html>
> CSS: <http://www.gunlaug.no/tos/alien/id/test_09_0502_files/layout00.css>
>
> Yes, it is backwards (hacking both old and new Gecko versions). I've
> also ignored very old Geckos completely.
> However, when dealing with a case that falls apart when subjected to the
> slightest amount of font resizing in any browser anyway, such a solution
> doesn't really add serious problems.
Interesting. The hack you have is.
@-moz-document url-prefix() {
:root>body #login_form label input {margin-top: -1.3em;}
:root>body:not(:nth-child(0)):only-of-type>*|*:not(|*)
#login_form label input { margin-top: 0;}
}
Does this hack separate Firefox 3.0.1 ~ 3.0.10 from Firefox 3.5b4? I can
not test. This part of the hack,
|*:not(|
causes a parsing error. Is this fixed in Firefox 3.5b4? I must admit
that your hackery (possibly combining structural pseudo class support
and parsing errors) is hackier than mine. :-)
This is similar to a more recent test case on this list which I have
hacked to target Gecko 1.9.
<http://css-class.com/test/css/visformatting/float-inline-content3.htm>
With this hack.
img:not([class*=""]) {margin-top:-1.3em; border-right: 4px solid red;}
/* targeting Gecko 1.9 */
Does Firefox 3.5b4 now send those images above the text line? The same
test case but with your hack.
<http://css-class.com/test/css/visformatting/float-inline-content4.htm>
I may learn a thing or two about CSS.
> The best solution is always to leave new browser versions alone - not
> hack them, but if that's not an option...
>
> regards
> Georg
I would dare say to not hack something that is not present when the
source is changed. Yes with IE this may be done but this is Gecko we are
dealing with. Also this can cause confusion between these different bugs.
<https://bugzilla.mozilla.org/show_bug.cgi?id=50630>
<https://bugzilla.mozilla.org/show_bug.cgi?id=441259>
The former does not effect Safari. Both bugs have been fixed with
Firefox 3.5b4? The later is still present in Safari.
--
Alan http://css-class.com/
Armies Cannot Stop An Idea Whose Time Has Come. - Victor Hugo
______________________________________________________________________
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
