|
|
Posted by Ben C on 05/30/07 07:30
On 2007-05-29, dorayme <doraymeRidThis@optusnet.com.au> wrote:
> In article <f3gkoj$r0a$00$1@news.t-online.com>,
> Knut Krueger <knut.krueger@usa.com> wrote:
>
>> dorayme schrieb:
>> > In article <hIH6i.170761$EZ5.107427@reader1.news.saunalahti.fi>,
>> > "Jukka K. Korpela" <jkorpela@cs.tut.fi> wrote:
>> >
>> >> Browsers often interpret a lone <br> as a request for empty line, but
>> >> don't rely on such (mis)behavior.
>> >
>> > On all my Mac browsers I don't get an _empty_ line.
>> >
>> That's a problem - verifying the pages is very difficult.
>> Firefox f.e is different on Mac and Windows and maybe different on
>> Linux. Seems that there is a need for at least three systems to test all
>> possible bugs and variations of the pages ...
>>
>
> Is FF different on Windows cf to Mac? I have so far been
> supposing not, thinking that I would have heard by now surely?
I doubt it, but what did you mean by a "[non-]_empty_" line? A line
containing nothing but one line-height's worth of space is what a lone
<br> gives me on my Linux version of FF.
e.g.
<style type="text/css">
div { font-size: xx-large; background-color: pink }
</style>
...
<body>
<div>
<br>
</div>
</body>
[Back to original message]
|