On Wed, 25 Mar 2015 21:31:51 +0100, Jonas Sicking jo...@sicking.cc wrote:
Is this really something we should tie to the pushState/replaceState API?
It seems like websites that lazily add more content as the user scroll
down, like the facebook feed or twitter feed, might not use
On Thu, 26 Mar 2015 01:47:57 +0100, Martin Janecke whatwg@prlbr.com
wrote:
Am .03.2015, 16:08 Uhr, schrieb Simon Pieters sim...@opera.com:
[…]
It seems to me that there are two use cases:
1. variable-size image map
2. art direction image map
(1) is more common than (2).
Yes, you're
You still haven't demonstrated that anyone but you want the ability to
stop a meta refresh, though.
I think it's a matter of proper design philosophy to say no to this. Meta
refresh is an ancient quick hack from the Netscape/IE4 era to declaratively
specify a reload/redirect intent,
On Thu, 26 Mar 2015 08:28:37 +0100, Karl Dubost k...@la-grange.net wrote:
Andrea, Simon,
Le 25 mars 2015 à 23:08, Andrea Rendine master.skywalker...@gmail.com
a écrit :
I think Refresh as an HTTP header is not specified anywhere, so per
spec
it shouldn't work. However I think browsers all
On Wed, 25 Mar 2015 15:08:41 +0100, Andrea Rendine
master.skywalker...@gmail.com wrote:
Having a writable property would allow e.g. to delay the refresh
Why is that useful?
Let's say, for example, that Refresh could be delayed if another timed
event is happening on the page (say, for
Am .03.2015, 11:10 Uhr, schrieb Simon Pieters sim...@opera.com:
On Thu, 26 Mar 2015 01:47:57 +0100, Martin Janecke
whatwg@prlbr.com wrote:
Am .03.2015, 16:08 Uhr, schrieb Simon Pieters sim...@opera.com:
[…]
It seems to me that there are two use cases:
1. variable-size image map
2.
Simon:
I think extremely few actually care about XHTML, but the other issue is
probably more relevant.
I think that the spec takes care of XHTML and that there's a W3 candidate
recommendation spec about polyglot markup. XHTML addresses some issues
and creates others, but actually I trust it for
That's evidence that I'm not smart enough. I never search on StackOverflow,
I usually g***le it out.
Some fellow people who want to stop the power of meta, then. (the first 2
questions for sure, and even more below)
If meta were changeable or removable before the refresh action is fired,
then it
On Thu, 26 Mar 2015 13:11:15 +0100, Andrea Rendine
master.skywalker...@gmail.com wrote:
You still haven't demonstrated that anyone but you want the ability to
stop a meta refresh, though.
I guess it's extremely difficult to demonstrate what people want to do
when
a feature is not currently
Therefore he gets a site without non-declarative interactivity, from
complex form validations and animations to complex page refresh logic.
Native form validation, CSS animations, still keep working with JS
disabled. Again, disabling JS does not mean refusing animations.
Does this mean that
On Tue, 17 Mar 2015, Andrea Rendine wrote:
Changes to make:
- The properties
dc.created,
dc.date.issued,
dc.dateCopyrighted,
dc.dateSubmitted,
dc.license,
dc.mediator,
dc.medium,
dc.modified,
dc.provenance,
dc.references,
dc.temporal,
dc.valid
are to be REMOVED because not
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
On Thu, 26 Mar 2015 17:10:56 +0100, Andrea Rendine
master.skywalker...@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
On Thu, 26 Mar 2015 14:37:17 +0100, Andrea Rendine
master.skywalker...@gmail.com wrote:
Some fellow people who want to stop the power of meta, then. (the
first 2
questions for sure, and even more below)
http://stackoverflow.com/questions/28435865/can-i-stop-a-meta-refresh-using-javascript
On Thu, Mar 26, 2015 at 1:22 AM, Majid Valipour maji...@google.com wrote:
My only concern is to make sure that these new methods replace
history.pushState() and history.replaceState() in the spec. Otherwise I feel
the benefits of a cleaner API is not worth the additional confusion of
having
Andrea, Simon,
Le 25 mars 2015 à 23:08, Andrea Rendine master.skywalker...@gmail.com a
écrit :
I think Refresh as an HTTP header is not specified anywhere, so per spec
it shouldn't work. However I think browsers all support it, so it would be
good to specify it.
Indeed. It was
On Mar 24, 2015, at 10:57 PM, Matthew Sotoudeh matthew...@outlook.com wrote:
Hello!
By way of introduction, I'm an author who reads some of these mailing lists
but (almost) never replies.
This proposal is quite interesting, wanted to throw in my two cents as well:
1. Would
On Thu, 26 Mar 2015 16:15:21 +0100, Andrea Rendine
master.skywalker...@gmail.com wrote:
..Simon, there's no use case where meta cannot be substituted by a
JS-only solution. The point is, what happens to the JS-only solution in
cases where JS is not usable for any reason?
A JS-only solution
..Simon, there's no use case where meta cannot be substituted by a
JS-only solution. The point is, what happens to the JS-only solution in
cases where JS is not usable for any reason? Usually fallback content can
be hidden or removed somehow, but meta makes it impossible. Does this
mean that meta
On Thu, Mar 26, 2015 at 3:57 PM, Majid Valipour maji...@google.com wrote:
That is fair. Assuming clear documentation helps alleviate potential
confusion I am fine with deprecation route. I suppose the purpose of the
spec is to not only document the current recommended behavior but also
capture
The point is, what happens to the JS-only solution in cases where JS is not
usable for any reason?
It will not run. The user has chosen to either disable JS or use a
non-supporting UA. Therefore he gets a site without non-declarative
interactivity, from complex form validations and animations
21 matches
Mail list logo
