Prev: See and Enjoy Indian Girls Gallery.
Next: Mousewheel event does not support DOM0 in FF
From: Joe Nine on 3 Jun 2010 11:31
Thomas 'PointedEars' Lahn wrote:
> Joe Nine wrote:
>
>> Thomas 'PointedEars' Lahn wrote:
>>> Joe Nine wrote:
>>>> There is a case where I deliberately create an iframe element with a
>>>> blank src and it doesn't [appear to] load the html into it. If it did,
>>>> then it would recurse ad-infinitum. A chain of iframe turtles all the
>>>> way down.
>>> You realize, of course, that this a case as I described, where it makes a
>>> lot of sense for a UA to prune the HTTP request. Still you should not
>>> rely on that the iframe stays blank, then. So, again, do not do this.
>> Unfortunately I need to do this because of this 5 year old Firefox bug:
>
> No, you don't. You have every freedom to use a proper default value.
>
> PointedEars

I'd like to use a default value I really would, but the html page that
I'm loading into the iframe wants to be fully reloaded each time the
browser is refreshed, like it deserves to be. It's an entire html page
and should be treated with respect and get fully reloaded. Firefox
doesn't treat it like that though, it doesn't fully reload the iframe.

The simplest example of how to recreate this problem is to load a html
page that (itself) makes a 50/50 random decision on whether to show one
thing or another. On all browsers except Firefox, as you keep hitting
refresh (e.g. F5) then you'll see the iframe making a 50/50 choice. If
you perform that test on Firefox, you'll see that whatever the initial
50/50 choice is, that's what it will display on every single refresh.
Only a hard refresh (e.g. Ctrl-F5) will force it to bring up a new 50/50
choice and subsequent soft refreshes will repeatedly show that choice.

If an iframe is meant to be a fully-privileged html container in it's
own right, then it deserves to be re-constructed and re-parsed
completely on a refresh.
From: Thomas 'PointedEars' Lahn on 3 Jun 2010 13:51
Joe Nine wrote:

> Thomas 'PointedEars' Lahn wrote:
>> Joe Nine wrote:
>>> Thomas 'PointedEars' Lahn wrote:
>>>> Joe Nine wrote:
>>>>> There is a case where I deliberately create an iframe element with a
>>>>> blank src and it doesn't [appear to] load the html into it. If it did,
>>>>> then it would recurse ad-infinitum. A chain of iframe turtles all the
>>>>> way down.
>>>> You realize, of course, that this a case as I described, where it makes
>>>> a lot of sense for a UA to prune the HTTP request. Still you should
>>>> not rely on that the iframe stays blank, then. So, again, do not do
>>>> this.
>>> Unfortunately I need to do this because of this 5 year old Firefox bug:
>> No, you don't. You have every freedom to use a proper default value.
>
> I'd like to use a default value I really would, but the html page that
> I'm loading into the iframe wants to be fully reloaded each time the
> browser is refreshed, like it deserves to be. It's an entire html page
> and should be treated with respect and get fully reloaded. Firefox
> doesn't treat it like that though, it doesn't fully reload the iframe.

That problem does not appear to exist in "Mozilla/5.0 (X11; U; Linux i686;
en-US; rv:1.9.2.3) Gecko/20100404 Iceweasel/3.6.3 (like Firefox/3.6.3)
GTB7.0" anymore. In any event, I find it unlikely that using a default
empty string is necessary or sufficient to work around this problem.

You should also stop talking about technical entities as if they were
people. It makes you look a bit naive. There is also no `html page', there
is an _HTML_ _document_.

And please stop quoting my signature.


PointedEars
--
Danny Goodman's books are out of date and teach practices that are
positively harmful for cross-browser scripting.
-- Richard Cornford, cljs, <cife6q$253$1$8300dec7(a)news.demon.co.uk> (2004)
From: Joe Nine on 3 Jun 2010 14:07
Thomas 'PointedEars' Lahn wrote:
> Joe Nine wrote:
>
>> Thomas 'PointedEars' Lahn wrote:
>>> Joe Nine wrote:
>>>> Thomas 'PointedEars' Lahn wrote:
>>>>> Joe Nine wrote:
>>>>>> There is a case where I deliberately create an iframe element with a
>>>>>> blank src and it doesn't [appear to] load the html into it. If it did,
>>>>>> then it would recurse ad-infinitum. A chain of iframe turtles all the
>>>>>> way down.
>>>>> You realize, of course, that this a case as I described, where it makes
>>>>> a lot of sense for a UA to prune the HTTP request. Still you should
>>>>> not rely on that the iframe stays blank, then. So, again, do not do
>>>>> this.
>>>> Unfortunately I need to do this because of this 5 year old Firefox bug:
>>> No, you don't. You have every freedom to use a proper default value.
>> I'd like to use a default value I really would, but the html page that
>> I'm loading into the iframe wants to be fully reloaded each time the
>> browser is refreshed, like it deserves to be. It's an entire html page
>> and should be treated with respect and get fully reloaded. Firefox
>> doesn't treat it like that though, it doesn't fully reload the iframe.
>
> That problem does not appear to exist in "Mozilla/5.0 (X11; U; Linux i686;
> en-US; rv:1.9.2.3) Gecko/20100404 Iceweasel/3.6.3 (like Firefox/3.6.3)
> GTB7.0" anymore. In any event, I find it unlikely that using a default
> empty string is necessary or sufficient to work around this problem.

Well, I'm happy with the solution. It works for me.

> You should also stop talking about technical entities as if they were
> people. It makes you look a bit naive. There is also no `html page', there
> is an _HTML_ _document_.

I like to give them some personality. I don't want to be cold and
abstract to them. HTML pages have feelings too :) The W3 refer to HTML
pages here: http://www.w3.org/MarkUp/Guide/

> And please stop quoting my signature.
>
> PointedEars

I haven't quoted your sig. Thunderbird automatically removes it when I
hit reply.
First  |  Prev  | 
Pages: 1 2 3 4 5
Prev: See and Enjoy Indian Girls Gallery.
Next: Mousewheel event does not support DOM0 in FF