https://docs.google.com/spreadsheets/d/1y8LAcvyna4ph2WQvTb4gjOIvEEGzm-zIBOVYuyDfneU/edit?usp=sharing
cheers,
--
Simon Pieters
https://bocoup.com/
this API.
cheers
--
Simon Pieters
Opera Software
the spec says.
Which brings me back to my claim that the spec is not clear enough: one
of you two is wrong, which isn't really a situation that should arise
with a clear spec.
I have tried to clarify this in https://github.com/whatwg/html/pull/1799.
cheers
--
Simon Pieters
Opera Software
be
room in future for (start, end) parameters?
There is always room for adding convenience APIs, it's a matter of
demonstrating that it's a common enough need to make it worth the cost of
adding it.
https://wiki.whatwg.org/wiki/FAQ#Where.27s_the_harm_in_adding.E2.80.94
HTH,
--
Simon Pieters
Opera Software
ck-api:the-audio-element
for an example.
--
Simon Pieters
Opera Software
On Wed, 07 Oct 2015 07:12:16 +0200, Anne van Kesteren
wrote:
On Wed, Nov 26, 2014 at 9:50 AM, Simon Pieters wrote:
Make the end tag optional and have , and generate
implied end tags. (Maybe other tags like and can
also
imply .) The label attribute be honored if specified
On Thu, 09 Apr 2015 09:50:34 +0200, Simon Pieters wrote:
I don't disagree here. I just don't come to the conclusion that we
should have an API to test everything under the sun. I don't mind
changing or adding things to help feature-test things that are not
currently testab
ion that we should
have an API to test everything under the sun. I don't mind changing or
adding things to help feature-test things that are not currently testable
in compliant implementations.
--
Simon Pieters
Opera Software
On Wed, 08 Apr 2015 14:46:44 +0200, Mikko Rantalainen
wrote:
Simon Pieters (2015-04-08 11:07 Europe/Helsinki):
On Wed, 08 Apr 2015 07:55:26 +0200, Mikko Rantalainen
wrote:
The section 12.2.3.3 The list of active formatting elements
(https://html.spec.whatwg.org/multipage/syntax.html#the
r.)
What is the input that triggers this? I fail to come up with a list of
active formatting elements that makes the reconstruct algorithm have a
marker as entry in step 8.
--
Simon Pieters
Opera Software
rm-tests
for cross-browser tests.
For , we could solve the feature-testing problem by normalizing
the case for supported keywords but not unsupported keywords, so you can
check with .rel or .relList:
function preloadSupported() {
var link = document.createElement('link');
link.rel = 'PRELOAD';
return link.rel == 'preload';
}
--
Simon Pieters
Opera Software
he timeout, which is entirely reasonable.
--
Simon Pieters
Opera Software
where you want to fallback
to when JS is enabled but still fails to run. I didn't see that
being a requirement in the stackoverflow threads.
--
Simon Pieters
Opera Software
/questions/16289798/button-to-temporarily-disable-stop-meta-tag-refresh
These can be solved with JS-only refresh, as far as I can tell.
Any others?
--
Simon Pieters
Opera Software
not.
Alternatively you could check stackoverflow.
http://stackoverflow.com/search?q=stop+meta+refresh
Would any of those benefit from being able to stop meta refresh, and
JS-only redirect or are not enough?
--
Simon Pieters
Opera Software
On Thu, 26 Mar 2015 01:47:57 +0100, Martin Janecke
wrote:
Am .03.2015, 16:08 Uhr, schrieb Simon Pieters :
[…]
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 right.
If there is implem
haven't demonstrated that anyone but you want the ability to
stop a meta refresh, though.
--
Simon Pieters
Opera Software
basis or on a
per-navigation basis? If per-page, is it enough to just be able to turn it
off (i.e. not turn it on again)?
e.g.
history.restoreScroll = false;
or
history.disableRestoreScroll();
--
Simon Pieters
Opera Software
ta is fetched
using IE with the pref to follow meta refresh enabled, so zero-timeout
meta refresh to a different url will not be in the data set, I think.
--
Simon Pieters
Opera Software
it.
Besides that, the spec says that UAs may expose the time (and other
aspects) for a refresh event of the document and it also refers to the
possibility for a user to "cancel the redirect", while as of now users
aren't even informed, let alone allowed to interact with this event.
--
Simon Pieters
Opera Software
ls from browser vendors.
[1] The only new feature I'm aware of since HTML4 is
HTMLMapElement#images. This feature has not been implemented by anyone, so
unless somone suddenly shows interest implementing it, it will most likely
be removed again.
https://www.w3.org/Bugs/Public/show_bug.c
On Fri, 20 Mar 2015 20:22:28 +0100, Martin Janecke
wrote:
Am .03.2015, 13:10 Uhr, schrieb Simon Pieters :
Please leave out syntax proposals for now. What I think is needed first
to drive this forward is:
* Use cases. Why do you need this?
In general it's needed to allow geom
pages that work around the lack of this feature.
* Why are alternatives like CSS-positioned links or SVG not better?
* Is there implementation interest among browser vendors?
--
Simon Pieters
Opera Software
doing the same for could be Web
compatible,
and Safari's behavior makes that seem likely, that seems like a pretty
good
outcome.
Let's try it.
https://code.google.com/p/chromium/issues/detail?id=413272#c6
--
Simon Pieters
Opera Software
solved on the server. Are there other use cases?
--
Simon Pieters
Opera Software
h; likely that event can be renamed.
https://html.spec.whatwg.org/multipage/embedded-content.html#the-video-element:event-media-resize
--
Simon Pieters
Opera Software
On Wed, 07 Jan 2015 08:55:02 +0100, Julian Reschke
wrote:
On 2015-01-07 08:52, Simon Pieters wrote:
...
I hear (a) these pages have been broken in IE for a long time, and (b)
only 23 (?) pages in your DB are found.
Right.
So why not just leave them broken?
It's a worse
On Tue, 06 Jan 2015 08:35:54 +0100, Julian Reschke
wrote:
On 2014-12-11 09:09, Simon Pieters wrote:
The spec's parsing rules of meta refresh causes infinite reloading on
some pages. In particular, the spec requires the "url=" to be present,
but there are pages that om
s*[\"']?\s*\d+\s*;\s*url=")
GROUP BY page
23 rows.
I also noticed that Gecko allows the number to be omitted. I only found
one page doing that and it was using content=";URL="> so it seems we can fail parsing for that case.
--
Simon Pieters
Opera Software
On Mon, 08 Dec 2014 21:50:56 +0100, Simon Pieters wrote:
On Thu, 27 Nov 2014 01:15:20 +0100, Ian Hickson wrote:
On Wed, 26 Nov 2014, Simon Pieters wrote:
- Make the end tag optional and have , and
generate implied end tags. (Maybe other tags like and
can also imply .) The label
On Mon, 08 Dec 2014 21:50:56 +0100, Simon Pieters wrote:
SELECT COUNT(*) as num,
CASE
WHEN REGEXP_MATCH(LOWER(body),
r']*>(\s*[^<]+)+\s*') THEN "has content"
ELSE "no content"
END as stat
FROM [httparchive:runs.2014_08_15_requests_body]
W
On Mon, 08 Dec 2014 21:50:56 +0100, Simon Pieters wrote:
On Thu, 27 Nov 2014 01:15:20 +0100, Ian Hickson wrote:
On Wed, 26 Nov 2014, Simon Pieters wrote:
- Make the end tag optional and have , and
generate implied end tags. (Maybe other tags like and
can also imply .) The label
On Thu, 27 Nov 2014 01:15:20 +0100, Ian Hickson wrote:
On Wed, 26 Nov 2014, Simon Pieters wrote:
- Make the end tag optional and have , and
generate implied end tags. (Maybe other tags like and
can also imply .) The label attribute be honored if
specified, otherwise use the textContent
d can also
imply .) The label attribute be honored if specified, otherwise
use the textContent with leading and trailing whitespace trimmed.
This would allow either syntax unless I'm missing something.
--
Simon Pieters
Opera Software
t from better interop. For instance
other shapes that are possible in canvas are not supported by image maps.
It does not do anything differently for /srcset. It's considered
a legacy feature.
Maybe inline SVG is a better choice for authors today?
--
Simon Pieters
Opera Software
On Sat, 01 Nov 2014 02:34:42 +0200, Ilya Grigorik
wrote:
Before we get into the pros and cons of "scoped", I think it's important
to
highlight that in body is already a fact of life:
1) developers already put tags in body, specs be damned.
2) all browsers support tags in body because of
On Wed, 29 Oct 2014 23:46:28 +0200, Ilya Grigorik
wrote:
(based on discussion at the webperf group meeting at TPAC... hopefully I
captured the discussion correctly. If not, please jump in!)
HTML5 spec: "If the rel attribute is used, the element is restricted to
the
head element." [1]
Abo
s return empty string in the first step if url
is null.
Does that help?
--
Simon Pieters
Opera Software
g.org.
cheers
--
Simon Pieters
Opera Software
e element be in that list?
Thanks and cheers,
Ezequiel
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26981
--
Simon Pieters
Opera Software
On Sat, 23 Aug 2014 02:44:23 +0200, Ian Hickson wrote:
On Wed, 12 Mar 2014, Boris Zbarsky wrote:
I realize no one would write actual code like this; the real-life use
case I'm
worried about would be more like this:
// img is already loaded sometimes
// Would like to observe a new loa
andscape/ ) and dropped the Changes (covered by
http://platform.html5.org/history/ ).
https://github.com/whatwg/html-differences/commit/a34fa020d2e2c17bb84fe963dc3f8de2250c31c4
https://github.com/whatwg/html-differences/commit/06499f22bcfd5f72ac1e7b3f3f3e4863e2db9c0b
--
Simon Pieters
Opera Software
s hope this is worth
addressing.
I don’t have anything else to add :)
I've removed the Changes section now. Redundant with
http://platform.html5.org/history/
https://github.com/whatwg/html-differences/commit/06499f22bcfd5f72ac1e7b3f3f3e4863e2db9c0b
--
Simon Pieters
Opera Software
anges at this point.
Feedback is very much welcome.
cheers
--
Simon Pieters
Opera Software
On Wed, 05 Feb 2014 15:11:32 +0100, David Carlisle
wrote:
On 05/02/2014 13:24, Simon Pieters wrote:
Is there a situation in which it is conforming to use html:title
outside the in a document where the root is html:html? In
math:annotation-xml?
My reading is yes, and validator.nu at
eb-apps/current-work/multipage/the-map-element.html#svg-0
Is there a situation in which it is conforming to use html:title outside
the in a document where the root is html:html? In
math:annotation-xml?
--
Simon Pieters
Opera Software
with focus, no element, but still a document element.
[...]
If the root element is html in the HTML namespace,
you have that behavior, and otherwise you return the root element
itself?
That sounds good to me.
--
Simon Pieters
Opera Software
to see an implementation that implements the spec
literally in order to better assess whether the specification is good or
not. I'm not saying that you have any obligation to do that, though; maybe
you have different goals. :-)
--
Simon Pieters
Opera Software
e is that I don't expose the to scripts.
What is the motivation?
That may make it even simpler, because you can't have odd cases like
author moving/removing the controlling img or setting values directly on
img that conflict with picture's definitions.
I don't see what would conflict in my proposal.
--
Simon Pieters
Opera Software
e to
evaluate a MQ, to avoid the wasted download.
but back on the main thread, the source selection algorithm will pick
the right picture a little bit later.
--
Simon Pieters
Opera Software
weirder.
--
Simon Pieters
Opera Software
previously the first). Similarly when an img element is removed, the
(new) first img child needs to run the selection algorithm. Although it
involves more checks, I think it seems saner to have only the first img
use the s.
--
Simon Pieters
Opera Software
eated flag is set. When img is inserted to
the document, if the parser-created flag is set, the flag is first unset
and then 'update the image data' is run but without the await a stable
state step.
--
Simon Pieters
Opera Software
On Thu, 31 Oct 2013 06:48:00 +0100, Boris Zbarsky wrote:
On 10/23/13 4:39 AM, Simon Pieters wrote:
Or maybe we could remove the name lookup thing altogether for
Element.getElementsByTagName et al?
Hmm. There are some compat worries here; do we have any indications
that this name lookup
While true, in practice pretty much no one uses the name getter on that
object, so nothing right now forces browsers to implement it in a
particularly efficient (as opposed to simple) way.
Or maybe we could remove the name lookup thing altogether for
Element.getElementsByTagName et al?
--
best
thing to do?
What if another document also has a reference to the port, does it still
get disentangled when the owner gets navigated?
--
Simon Pieters
Opera Software
The API is intended to be used for escaping CSS strings too. Also, I think
most Web developers don't think in terms of CSS tokens.
Serialize seems a bit wrong since the input isn't an object.
--
Simon Pieters
Opera Software
d actually write "CSS.escape", so that's basically the longer,
different name. Is that sufficient?
--
Simon Pieters
Opera Software
bcc www-style, context
http://lists.w3.org/Archives/Public/public-whatwg-archive/2013Oct/0075.html
On Thu, 10 Oct 2013 13:06:58 +0200, Simon Pieters wrote:
So, in cluclusion, it appears that there is *some* demand for this. The
common case is escaping as ident. An API to escape as ident
f093070baa2d7e405cdecaa055108c/app/js/vis.js
I did however find more instances (528) by searching for "escapeSelector":
https://github.com/search?l=javascript&q=escapeSelector&ref=searchresults&type=Code
So, in cluclusion, it appears that there is *some* demand for this. The
common case is escaping as ident. An API to escape as ident could be used
for escaping strings, too. In order to not make people think more than
just remembering to escape at all, it might be a good idea to just have
one API to serve both cases, e.g. CSS.escape(foo).
I don't think that adding an API to escape a CSS ident means that it's a
good idea to not have e.g. getElementById on DocumentFragment. Most people
don't escape their stuff, so only providing a selector API that requires
escaping seems like the net effect would be more buggy code.
--
Simon Pieters
Opera Software
on that we couldn't also fire the event if the
other side is forcefully terminated through a navigation or a
Worker.terminate() call?
Does navigation disentangle ports? I don't think it necessarily does, at
least per spec.
--
Simon Pieters
Opera Software
working content
attribute for a given element. That's just confusing.
--
Simon Pieters
Opera Software
y, invalid
descriptors should just be ignored so that "2x 500tt bla" will results
in a
density of 2, width of infinity and height of infinity.
Is that correct?
Yes.
Step 13.6. could say "Otherwise, do nothing", but that's implied.
Yoav
[1]
http://www.whatwg.org/specs/web-apps/current-work/multipage/embedded-content-1.html#processing-the-image-candidates
--
Simon Pieters
Opera Software
`this` will be wrong. But you can add
.bind(document) to fix that.
--
Simon Pieters
Opera Software
On Fri, 13 Sep 2013 12:32:43 +0200, Robin Berjon wrote:
On 29/08/2013 15:58 , Simon Pieters wrote:
On Thu, 29 Aug 2013 15:02:48 +0200, Anne van Kesteren
wrote:
On Thu, Aug 29, 2013 at 1:19 PM, Jake Archibald
wrote:
Causing a network error in existing browsers is a shame.
It seems to
erface "Document" and is an "XML document", even
for text/html if I read the spec correctly)
For instance the createHTMLDocument() case currently supports named getter
in Gecko but not in Blink.
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2519
--
Simon Pieters
Opera Software
quot; mean here, is it to handle cases where the UA
force-enables the controls without adding the controls attribute to
the DOM?
Yes.
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html#expose-a-user-interface-to-the-user
--
Simon Pieters
Opera Software
ute?
That might be good so that the behavior is consistent between browsers.
However, I think it should be conditional on whether the controls are
visible rather than whether the controls attribute is present.
--
Simon Pieters
Opera Software
On Fri, 06 Sep 2013 16:42:47 +0200, Boris Zbarsky wrote:
On 9/6/13 8:20 AM, Simon Pieters wrote:
So the use case is getting an element by id with an "untrusted" id as
input, in an element or document fragment as opposed to the document?
Or getting elements by tag name in a documen
rrent-work/multipage/forms.html#dom-label-control
but it only works when in a document. Maybe that should be changed, though.
--
Simon Pieters
Opera Software
On Fri, 06 Sep 2013 14:21:24 +0200, Scott González
wrote:
On Fri, Sep 6, 2013 at 8:20 AM, Simon Pieters wrote:
So the use case is getting an element by id with an "untrusted" id as
input, in an element or document fragment as opposed to the document?
Yes. Take the example
:
http://mothereff.in/css-escapes
So the use case is getting an element by id with an "untrusted" id as
input, in an element or document fragment as opposed to the document?
--
Simon Pieters
Opera Software
at all in
http://webdevdata.org/ data set 18/06/2013. So maybe we could use a string
like that in the path and have a graceful fallback path in legacy browsers
that work in existing servers.
--
Simon Pieters
Opera Software
r one
thing to all other things that have similar shape. I'd rather simplify
controlsTarget to be a boolean since that also addresses the problem at
hand.
--
Simon Pieters
Opera Software
even what was
being clicked (as a string).
--
Simon Pieters
Opera Software
ge fixes this.
You are still notified by a 'play' event when the user clicks play on the
native controls, so you can do something when the user clicks play on the
native controls.
--
Simon Pieters
Opera Software
. And mine has the performance issue. How
about we don't return the 'binary' string in case the 2nd parameter is
provided in my case?
That works for me.
--
Simon Pieters
Opera Software
be 1, newarr[1] should be 2 and newarr[2] should be 3.
Is there a reason to support an arbitrary typed array for atob rather than
returning a new typed array?
e.g.
var newarr = atob(encodedData, {typedarray:true});
(I'm not sure which view is most appropriate to return.)
--
Simon Pieters
Opera Software
o getContext, eg. to
see if null would be returned if a particular option is provided, which
supportsContext allows. (I don't know if there are any cases where this
actually happens, since most options are "best effort" and don't cause
context creation to fail if they're not
ttribute itself would be omitted from the objects that
implement that interface — leaving the attribute on the object but making
it return null or throw an exception is insufficient.
]]
http://www.whatwg.org/specs/web-apps/current-work/multipage/infrastructure.html#extensibility
--
Simo
ject. This does
basically the same thing as supportsContext, except that it would also
work for pages that already do feature detection based on the interface
object.
--
Simon Pieters
Opera Software
le who could help me move this idea forward.
Who should I ping/contact/harass?
What would be useful for me:
* use cases for the feature.
* URLs to existing pages that work around the lack of this feature.
* stated implementation interest from browser vendors.
Please comment further in the bug.
Path2d and Shape2d sound reasonable. I don't think there's a immediate need to
harmonize gradients so we probably want to keep CanvasGradient.
Do you prefer the lowercase 'd' instead of the uppercase 'D'?
CanvasRenderingContext2D has it uppercase.
--
Simon Pieters
Opera Software
On 6/17/13 1:44 PM, Boris Zbarsky wrote:
On 6/17/13 6:05 AM, Simon Pieters wrote:
What's in CSSOM now is "tainting".
Sort of. I think of tainting as "you can write to it but read from
it", but what's in CSSOM is "you can't touch it".
True.
[0].cssRules)
Since this currently throws in Firefox, it's likely that there isn't a
big Web compat problem to not support this. I think doesn't
support the equivalent thing, either, per spec (although a is a
bit different in that it can have lots of images drawn on it from
different origins).
--
Simon Pieters
Opera Software
of the name as parameters to a Bugzilla bug entry.
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21916
--
Simon Pieters
Opera Software
ue is the byte string `text/html;charset=utf-8`, and body is the
empty string.
Otherwise, return a network error.
]]
(BTW should body be the empty byte string above?)
--
Simon Pieters
Opera Software
ng, which might be a good idea.
Or
* Differences of W3C HTML5/WHATWG HTML from HTML4
* Differences of WHATWG HTML/W3C HTML5 from HTML4
* HTML5 differences from HTML4 (the W3C title)
Anyway, I agree that "HTML differences from HTML4" sounds confusing and
any of the above is better
details, to begin with.
It's more intended to be an overview. Can you give an example of something
that is too detailed and suggest the level of detail that would be more
appropriate?
Is this for authors who consider moving from HTML 4.01 to HTML 5?
Yes.
Then I think it should primarily specify what HTML 4.01 features are
forbidden in HTML 5, then the extensions.
Thanks, that's useful feedback.
--
Simon Pieters
Opera Software
ouble its size, respectively).
I understand the amount of space it takes. I still don't understand what
the problem is. Is it that people look at the scrollbar and think "oh wow
this document is too long, I'm not gonna bother reading it at all."? Or
something else?
oblem?
--
Simon Pieters
Opera Software
On Fri, 03 May 2013 18:20:51 +0200, Jukka K. Korpela
wrote:
2013-05-03 18:37, Simon Pieters wrote:
The past few days I've been working on updating the HTML differences
from HTML4 document, which is a deliverable of the W3C HTML WG but is
now also available as a version with the W
Hi
The past few days I've been working on updating the HTML differences from
HTML4 document, which is a deliverable of the W3C HTML WG but is now also
available as a version with the WHATWG style sheet:
http://html-differences.whatwg.org/
Review welcome. Please file bugs.
--
html5.org/r/4834
Context:
http://lists.w3.org/Archives/Public/public-whatwg-archive/2010Mar/thread.html#msg67
--
Simon Pieters
Opera Software
orkerUtils implements IDBEnvironment;
]]
https://dvcs.w3.org/hg/IndexedDB/raw-file/tip/Overview.html#requests
1: http://dev.w3.org/html5/workers/
On Thu, Mar 14, 2013 at 2:08 AM, Simon Pieters wrote:
The new canvas proxy stuff is supposed to make canvas work in workers,
but
I don't see any
would be. The last window the user interacted with maybe?
--
http://annevankesteren.nl/
--
Simon Pieters
Opera Software
;auto' useful in practice? Is it a behavior that authors or users
expect? I don't know, but my hunch is "no", and it would be more
straightforward to just use horizontal and let the author opt-in to
vertical with the attribute.
--
Simon Pieters
Opera Software
topic, however, if we are going to
add an attribute, it would be less verbose to use a boolean attribute:
--
Simon Pieters
Opera Software
rkers.
--
Simon Pieters
Opera Software
m to be in line with those currently in the list. Should they be
added to the spec?
BTW, the spec's list is not in alphabetical order.
--
Simon Pieters
Opera Software
1 - 100 of 710 matches
Mail list logo
