On Thu, 07 Jan 2016 20:12:44 +0100, Boris Zbarsky <bzbar...@mit.edu> wrote:
On 12/18/15 3:53 AM, Simon Pieters wrote:
Note that it requires liveness. Does that work for a frozen array?
No. You'd have to create a new array object at the point when you want
to update the set of
webidl-tests origin/pr/271
git push -u origin webidl-tests
--
Simon Pieters
Opera Software
On Fri, 18 Dec 2015 18:04:27 +0100, Olli Pettay <o...@pettay.fi> wrote:
On 12/18/2015 06:20 PM, Domenic Denicola wrote:
From: Simon Pieters [mailto:sim...@opera.com]
Note that it requires liveness. Does that work for a frozen array?
Frozen array instances are frozen and cannot
a
sequence?
--
Simon Pieters
Opera Software
On Thu, 02 Apr 2015 14:15:10 +0200, Simon Pieters sim...@opera.com wrote:
http://www.w3c-test.org/websockets/keeping-connection-open/001.html --
the test is wrong. Passing undefined means the argument is not present
per Web IDL, so this should not throw.
I assume you mean some other test
.
(Will have a look.)
--
Simon Pieters
Opera Software
On Thu, 02 Apr 2015 14:15:10 +0200, Simon Pieters sim...@opera.com wrote:
http://www.w3c-test.org/websockets/interfaces/WebSocket/readyState/003.html
looks wrong to me: the value it should get is in fact undefined, since
the property got deleted from the prototype.
(Will have a look
-connection-open/001.html
which is all-Timeout.
This test passes for me in Blink and Gecko. It has a meta indicating it
needs a long timeout. Is it a bug in the test runner being used here?
--
Simon Pieters
Opera Software
On Thu, 26 Mar 2015 16:37:28 +0100, Olli Pettay o...@pettay.fi wrote:
websockets/interfaces.html the test itself has bugs (uses old
idlharness.js?).
https://github.com/w3c/web-platform-tests/pull/1714
--
Simon Pieters
Opera Software
was written.
Spec now says [TreatNonObjectAsNull] so this should return the object, not
null.
https://html.spec.whatwg.org/multipage/webappapis.html#eventhandlernonnull
Fix: https://github.com/w3c/web-platform-tests/pull/1704
--
Simon Pieters
Opera Software
--
Simon Pieters
Opera Software
-16 BOM) and JSON response
(always decodes as utf-8).
--
Simon Pieters
Opera Software
On Mon, 23 Mar 2015 14:32:27 +0100, Hallvord Reiar Michaelsen Steen
hst...@mozilla.com wrote:
On Mon, Mar 23, 2015 at 1:45 PM, Simon Pieters sim...@opera.com wrote:
On Sun, 22 Mar 2015 23:13:20 +0100, Hallvord Reiar Michaelsen Steen
hst...@mozilla.com wrote:
Given a server which sends
increments whenever we undo, I would think that position
should be set to the undo stack's length - 1.
Simon
have the need to pass the context node as an
argument along with other nodes, just use before() and after() to insert
these other nodes? And even insert them one by one is fine?
Yeah.
--
Simon Pieters
Opera Software
doesn’t sound very optimal.
In all cases it would be just one reflow after the script has finished,
unless you force a reflow by asking for layout information (e.g.
offsetTop) between the mutations.
--
Simon Pieters
Opera Software
to
change them to use a more specific interface. How do you envision to solve
this? Should we assign element-specific interfaces to all post-HTML4
elements now, just in case? Or make new HTMLElement('ruby') create an
HTMLRubyElement? Something else?
--
Simon Pieters
Opera Software
I'd
give that a try to see if it fits the model. If not, would abstract
events or simply high-level events work? Sorry if these have already
been discussed and dismissed (haven't had much time to look through the
archives, tbh).
How about device-independent events?
--
Simon Pieters
Opera Software
On Fri, 12 Dec 2014 17:02:25 +0100, Frederico Knabben
f.knab...@cksource.com wrote:
On Friday, 12 December 2014 at 14:40, Simon Pieters wrote:
How about device-independent events?
Aren’t we missing what kinds of events we’re talking about? We would
just know that those events are device
:
[[
This constructor must be visible when the script's global object is
either a Window object or an object implementing the WorkerUtils
interface.
]]
Thoughts, Simon Odin?
Redundant with [Exposed].
Please use
https://html.spec.whatwg.org/multipage/comms.html#server-sent-events
when implementing
#host_general_conflict_header
From my reading though, the default implicit ARIA semantics are still UA
requirements, right?
Yes.
[...]
--
Simon Pieters
Opera Software
it is a problem.
http://www.w3.org/mid/op.ww3ecpo5idj3kv@simons-macbook-pro.local
--
Simon Pieters
Opera Software
place but still annotate some of them as
being a test for another section, you can do that with link rel=help.
--
Simon Pieters
Opera Software
).
Global attributes have the same issue.
So when we research if it's safe to add a new global attribute, it's not
enough to measure how often such an attribute is used in the wild. We need
to research bare names in event handlers also.
--
Simon Pieters
Opera Software
On Wed, 18 Dec 2013 11:58:07 +0100, Simon Pieters sim...@opera.com wrote:
On Tue, 17 Dec 2013 17:06:57 +0100, Boris Zbarsky bzbar...@mit.edu
wrote:
On 12/17/13 3:29 AM, Jonas Sicking wrote:
This is a good point. Would this have performance implications for
down-level browsers? I don't know
, the workers implementation report [IR] remains empty.
Simon - would you please add results for Presto?
Done.
First I ran the tests using https://bitbucket.org/ms2ger/test-runner/src
on a local server, but then I couldn't think of a straight-forward way to
put the results in the wiki so I
understand the motivation here. I'd
rather we remove the first exit criteria than try to punch conformance
holes in the spec for failing tests.
--
Simon Pieters
Opera Software
really like to see us start a level 2 of the spec. The
synchronous messaging channels is something else I'd like to see done
there.
/ Jonas
--
Simon Pieters
Opera Software
On Fri, 22 Nov 2013 03:33:51 +0100, Jonas Sicking jo...@sicking.cc wrote:
The only browser shipping SharedWorkers is Chrome (not sure if Opera
does too?),
Yes, both Presto-based (since Opera 10.60) and Chromium-based.
--
Simon Pieters
Opera Software
On Wed, 06 Nov 2013 01:17:31 +0100, Jonas Sicking jo...@sicking.cc wrote:
window.screen.orientation seems like a better way forward.
Why would window.screen.orientation be any more correctly implemented than
window.orientation?
--
Simon Pieters
Opera Software
On Tue, 29 Oct 2013 00:54:05 +0100, Anne van Kesteren ann...@annevk.nl
wrote:
We are considering not throwing in XML.
Only on getting innerHTML, though, right?
--
Simon Pieters
Opera Software
it is needed.
Guilty, and fixed - I obviously need to study that WebIDL spec in some
detail.. :-/
Pro tip: use http://www.w3.org/2009/07/webidl-check (I invoke it in my
Makefile for CSSOM).
--
Simon Pieters
Opera Software
On Tue, 08 Oct 2013 17:19:51 +0200, Boris Zbarsky bzbar...@mit.edu wrote:
On 10/8/13 7:47 AM, Simon Pieters wrote:
Pro tip: use http://www.w3.org/2009/07/webidl-check (I invoke it in my
Makefile for CSSOM).
Hmm. What makes sure this is updated when the spec is updated? I just
tried
/desired/common this is.
I would hardly call taking the length subtracting any characters
before the , and applying a multiplier parsing. You don't have to
look at any characters after the , at all.
Just applying a multiplying doesn't take percent-escaping into account,
though.
--
Simon Pieters
, per spec.
--
Simon Pieters
Opera Software
it to an empty string. Where is / should this be
spec'ed?
http://www.whatwg.org/specs/web-apps/current-work/multipage/dom.html#dom-document-referrer
The XHR spec doesn't seem to set the document's referrer, so the value
is the empty string per spec.
--
Simon Pieters
Opera Software
-
Set the error flag.
http://xhr.spec.whatwg.org/#dom-xmlhttprequest-statustext
-
If the error flag is set, return the empty string.
(I'm not sure where the spec says that the above case is a network error,
though.)
--
Simon Pieters
Opera Software
throw
when serialized? Or should we just drop that test and leave that spec
statement untested?
Why would you drop the test?
--
Simon Pieters
Opera Software
..? :-)
XML can't represent an empty document.
--
Simon Pieters
Opera Software
-device-adapt/#dom-interfaces
Is that sufficient?
--
Simon Pieters
Opera Software
On Wed, 15 May 2013 20:26:36 +0200, Dimitri Glazkov
dglaz...@chromium.org wrote:
On Tue, May 14, 2013 at 2:21 PM, Simon Pieters sim...@opera.com wrote:
That seems to be an argument based on aesthetics. That's worth
considering,
of course, but I think is a relatively weak argument
confusion shown last time I suggested this:
* This is not script src.
* This is not changing anything of the component itself.
--
Simon Pieters
Opera Software
is not typical.
Isn't it perfectly reasonable to expect that a different scheme/port
is running an entirely different application?
I agree that Selectors 4 should be changed here. URLs that differ only
by the scheme or port number should not be considered local.
--
Simon Sapin
= attribute of source, but I think that
should be dropped from the element anyway.
Something similar could be done for img srcset, maybe, which is a
different beast than source.
It's a bit verbose, but it's a lot less verbose than loading the content
twice.
--
Simon Pieters
Opera Software
.
If there is a chance to settle on what's right for any of these, it
would be awesome.
Alex
[1]
https://dvcs.w3.org/hg/editing/raw-file/tip/editing.html#the-defaultparagraphseparator-command
--
Simon Pieters
Opera Software
* The only available options are P and DIV
* Default is P
In Presto, yes.
Is that correct?
Thanks
Alex
--
Simon Pieters
Opera Software
() and createElement(img)
are equivalent and no additional magic is required. Same for new
Audio() and createElement(audio).
Not quite, actually. new Audio() sets the content attribute preload=auto.
--
Simon Pieters
Opera Software
/Workers/tests/submissions/Opera/
Simon (Web Workers' `Test Facilitator`) proposed in [1] the tests are
sufficient to test the CR's exit criteria.
If you have any comments, please send them to
public-webapps-testsu...@w3.org by March 28.
I've looked at all the files in
http://w3c-test.org
suggest we do that.
--
Simon Pieters
Opera Software
elements to load.
Documents are fairly heavy-weight and introducing several documents
into the mix means that we have to deal with issues like making sure
that those documents have the same behavior (for example, if HTML
elements in those documents uppercase the nodeName or not)
/ Jonas
--
Simon
is display: block; margin-top: 1em; margin-bottom: 1em;
font-family: monospace; white-space: pre; unicode-bidi: isolate;
--
Simon Pieters
Opera Software
... */
}
Before I make this change in Gecko I'd like to get consensus from other
implementers that we want this behaviour, and get the spec changed to
reflect that.
Sounds good to me.
Regards,
Chris Pearce.
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=779286#c18
--
Simon Pieters
On Mon, 18 Jun 2012 16:57:17 +0200, Kang-Hao (Kenny) Lu
kennyl...@csail.mit.edu wrote:
(12/06/18 22:45), Simon Pieters wrote:
I think we should instead either fix the old API (if it turns out to not
Break the Web) or live with past mistake (if it turns out it does). To
find out whether
, but I'd note that in the corner case
These are valid:
|a
*|a
My proposed spec change:
# If the group of selectors include namespace prefixes that need to
# be resolved, the implementation must raise a NAMESPACE_ERR
# exception.
s/NAMESPACE_ERR/SYNTAX_ERR/
--
Simon Pieters
Opera Software
to querySelector() in
nightly/aurora (or equivalent) in one or more browsers for some time.
--
Simon Pieters
Opera Software
elements. content-fit or some such.
Do you mean object-fit? I guess it would be nice for images to be
object-fit:contain in fullscreen. (Videos already are.)
--
Simon Pieters
Opera Software
(connection
could not be opened or something like that) added somewhere (again I
assume RFC 6455 isn't possible, but the IANA database and/or the W3C
spec).
As above.
best,
Jason
Mozilla
--
Simon Pieters
Opera Software
:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16635 )
-otherwise, return body
--
Simon Pieters
Opera Software
On Wed, 23 May 2012 06:21:21 +0200, Jason Duell jduell.mcb...@gmail.com
wrote:
On Mon, 21 May 2012 12:28:16 +0200, Simon Pieters sim...@opera.com
wrote:
4. If the connection could not be opened, either because a direct
connection failed or because any proxy used returned an error
use a
dedicated code for this case too.
Or throw an exception? Or queue the connection? I've touched on this
subject before, but we didn't reach any conclusion as to what the right
thing to do is.
Jason Duell
Mozilla
--
Simon Pieters
Opera Software
On Mon, 21 May 2012 12:28:16 +0200, Simon Pieters sim...@opera.com wrote:
On Wed, 16 May 2012 02:17:45 +0200, Jason Duell
jduell.mcb...@gmail.com wrote:
So the Web Socket spec is a little vague on how JS is notified when
the targeted web socket server is down/nonexistent/etc.
Firefox
tspanbar/tspan baz
--
Simon Pieters
Opera Software
an
original one, though I'm sure y'all have considered it before. :-)
--
Simon Pieters
Opera Software
On Wed, 09 May 2012 19:29:42 +0200, Ryosuke Niwa rn...@webkit.org wrote:
On May 9, 2012 10:26 AM, Simon Pieters sim...@opera.com wrote:
On Wed, 09 May 2012 19:01:42 +0200, Ian Hickson i...@hixie.ch wrote:
Quick alternative proposal that might work for both template parsing
away from
depending on the current style.
Yes, I would much prefer if specs currently using ReSpec moved towards
using algorithms like the HTML spec. It's much clearer and is less likely
to have gaping holes for edge cases.
--
Simon Pieters
Opera Software
always parses in
the in body insertion mode. I'd like to see that fixed before we try to
support foreign content in contextless innerHTML.
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16635
Any other tagName = HTMLBodyElement
--
Simon Pieters
Opera Software
XMLHttpRequest?
Is there existing content depending on BlobBuilder and its
ArrayBufferView
stuff?
I thought the idea was to not have BlobBuilder at all.
--
Anne van Kesteren
http://annevankesteren.nl/
--
Simon Pieters
Opera Software
compat breaking changes
proposed. Are there any particular parts you are worried about?
I proposed setting ports to null.
--
Simon Pieters
Opera Software
. It
might continue to work if we decide that it's needed for back compat,
but it seems like we eventually would be able to get rid of it given
how new the property still is.
/ Jonas
--
Simon Pieters
Opera Software
On Tue, 10 Apr 2012 14:01:47 +0200, Jarred Nicholls jar...@webkit.org
wrote:
On Tue, Apr 10, 2012 at 1:20 AM, Simon Pieters sim...@opera.com wrote:
On Wed, 04 Apr 2012 18:37:46 +0200, Jonas Sicking jo...@sicking.cc
wrote:
Sounds great to me. The ports attribute is basically useless except
type of .source to any just for this case.
Anne said the type could be (WindowProxy or MessagePort)?.
I am curious to see where this latest discussion on perhaps using a
different Event interface for connect events will lead...
--
Simon Pieters
Opera Software
.
--
Simon Pieters
Opera Software
instance seems
like a win to me.
I'd like to have an opinion from WebKit and Microsoft about this proposal.
Can someone comment or cc relevant people, please?
cheers
/ Jonas
On Wednesday, April 4, 2012, Simon Pieters wrote:
Hi,
In Opera Extensions we use something that resembles shared workers
as well.
I think shared workers hasn't seen wide adoption yet, so maybe changes
like this are still possible.
What do people think?
currently:
onconnect = function(e) { e.ports[0].postMessage('pong') }
proposed change:
onconnect = function(e) { e.source.postMessage('pong') }
--
Simon
On Mon, 02 Apr 2012 07:50:21 +0200, Boris Zbarsky bzbar...@mit.edu wrote:
On 4/2/12 1:33 AM, Simon Pieters wrote:
Yes, but what do they use for the origin of the Worker object itself?
Run a worker for the resulting absolute URL, with the script's browsing
context of the script that invoked
associated with a
different global than the constructor itself?
I believe some things in the HTML spec uses the entry script, at least for
the purpose of choosing origin or base URL. For instance: WebSocket,
Worker.
--
Simon Pieters
Opera Software
On Mon, 02 Apr 2012 07:20:27 +0200, Boris Zbarsky bzbar...@mit.edu wrote:
On 4/2/12 12:58 AM, Simon Pieters wrote:
I believe some things in the HTML spec uses the entry script, at least
for the purpose of choosing origin or base URL. For instance: WebSocket,
Worker.
Yes, but what do they use
in a browser; in a TCP-only
HTML5 environment with deprecated support for these
technologies such options would have no standing ground.
See PeerConnection in http://dev.w3.org/2011/webrtc/editor/webrtc.html
I hope this is helpful feedback.
Best wishes,
Rick van Rein
OpenFortress
--
Simon
than throwing an
exception?
--
Simon Pieters
Opera Software
On Tue, 28 Feb 2012 01:05:44 +0100, Glenn Maynard gl...@zewt.org wrote:
On Mon, Feb 27, 2012 at 5:34 PM, Arun Ranganathan
aranganat...@mozilla.comwrote:
Simon,
Is the relevant part of HTML sufficient to refer to?
http://dev.w3.org/html5/spec/Overview.html#utf-8
I was thinking
to be strings only, the best way to get
there is for everyone to remove support for constants and numbers at the
same time as they implement support for strings.
--
Simon Pieters
Opera Software
On Wed, 11 Jan 2012 16:39:48 +0100, Aryeh Gregor a...@aryeh.name wrote:
On Tue, Jan 10, 2012 at 3:50 PM, Ryosuke Niwa rn...@webkit.org wrote:
p has default margins. That alone is enough for us not to adopt p as
the default paragraph separator.
On Wed, Jan 11, 2012 at 5:15 AM, Simon Pieters
? If not, what definition should we use
to determine which documents get selections?
--
Simon Pieters
Opera Software
for the legacy feature first.
- Ryosuke
--
Simon Pieters
Opera Software
they implement the
default paragraph separator setting themselves.
which is confusing for many users.
It might be less a hassle to have maintainers of existing applications
insert a line of code that triggers legacy behavior, if this is crucial
for their application.
--
Simon Pieters
. As always, you can see how the
spec implementation behaves for various input by looking at
autoimplementation.html:
http://aryeh.name/spec/editcommands/autoimplementation.html#insertparagraph
--
Simon Pieters
Opera Software
://bookmark.people.com.cn/index.html has onclick=find()
These would both obviously get broken by the proposed find() API, unless
we actually do some sort of workaround for this problem...
-Boris
--
Simon Pieters
Opera Software
On Wed, 14 Dec 2011 09:15:12 +0100, Boris Zbarsky bzbar...@mit.edu wrote:
On 12/14/11 3:01 AM, Simon Pieters wrote:
What I have so far as a result is a list of about 1.7 million
barewords used across several tens of thousands of pages.
Do you have a more accurate figure for the number
amount of support at TPAC and
we're
hoping this will be adopted in the File API spec.
Thanks,
Adrian.
[1] http://www.w3.org/2011/11/01-webapps-minutes.html#item02
[2] http://pages.adrianba.net/w3c/FilesAndStreams.pdf
--
Simon Pieters
Opera Software
/Safari should add support for selectNodes?
--
Simon Pieters
Opera Software
/dnd.html#dom-find
Are Firefox and WebKit going to drop the old find()? Is there legacy
content that feature detects for find() and would break if it changed
semantics?
--
Simon Pieters
Opera Software
mean that some
authors can't use workers at all because their server uses charset and
they can't change it.
--
Simon Pieters
Opera Software
string.
If we have UA compat on that behavior, it makes more sense to
standardize it than to standardize the UTF-8-only thing, perhaps
Opera conforms to the spec and always decodes worker scripts as UTF-8.
--
Simon Pieters
Opera Software
On Fri, 18 Nov 2011 13:22:42 +0100, Julian Reschke julian.resc...@gmx.de
wrote:
On 2011-11-18 13:03, Simon Pieters wrote:
UTF-8-only for workers is deliberate. I don't see any reason to reject
scripts that have other charset. Rejecting the script would mean that
some authors can't use
other parts of the
platform disagree.
Why not? We have context-dependent treatment of MIME types already (e.g. a
text/html resource can be treated as a script).
--
Simon Pieters
Opera Software
.
Workers ignore the MIME type.
--
Simon Pieters
Opera Software
very possible to make work.
How?
--
Simon Pieters
Opera Software
a) - d).
In no case JS involved .. dialogs are browser builtin.
Does above make sense?
No, both error and close fire.
--
Simon Pieters
Opera Software
onerror only, or fire both.
The spec clearly requires both.
--
Simon Pieters
Opera Software
.
...
It seems to me you need to be more careful in your usage of RFC2119
keywords. Also see http://ln.hixie.ch/?start=1140242962count=1
--
Simon Pieters
Opera Software
1 - 100 of 156 matches
Mail list logo
