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

List:       whatwg
Subject:    Re: [whatwg] Page refresh interface
From:       Andrea Rendine <master.skywalker.88 () gmail ! com>
Date:       2015-03-26 20:09:41
Message-ID: CAGxST9n3k=C+y1S=jJkVb3Cm35+s5z9MFydhnFy0mrQR=2Y5fQ () mail ! gmail ! com
[Download RAW message or body]

Someone also said that "once it used to work" or that "it no longer works",
even if I don't feel I can trust it.
Also consider that <noscript> is somehow blunt as it detects whether JS is
disabled, but its content is not parsed if JS is enabled but for any
reason it doesn't work.

2015-03-26 20:21 GMT+01:00 Simon Pieters <simonp@opera.com>:

> On Thu, 26 Mar 2015 17:10:56 +0100, Andrea Rendine <
> master.skywalker.88@gmail.com> wrote:
>
>  http://stackoverflow.com/questions/3252743/using-
>> javascript-to-override-or-disable-meta-refresh-tag
>> This thread is quite full of examples with authors trying to remove <meta>
>> after it is loaded or to hide it inside <noscript>, two not viable
>> solutions.
>>
>
> It looks like the person who asked the question in that thread would be
> happy with <noscript> had it worked in the "cell phone browser" he was
> interested in. But it would be better without <noscript>, certainly. Also
> several people assumed that it would work to remove the element to stop the
> timeout, which is entirely reasonable.
>
>
> --
> Simon Pieters
> Opera Software
>
[prev in list] [next in list] [prev in thread] [next in thread]