the best we've got available to us.
It's always possible to fill in any gaps from other's personal IRC logs;
it's quite simple for Krijn to insert them if someone sends them to him.
For important things like telcons, RRSAgent is always brought into the
channel anyway.
--
Lachlan Hunt - Opera
it at this stage.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Moved from public-webapi to public-webapps. Original issue raised here:
http://lists.w3.org/Archives/Public/public-webapi/2008Feb/0053.html
(forgot to change the address to public-webapps, resending to correct
list. Sorry for duplicates)
Lachlan Hunt wrote:
* It's not clear which IDL
being
forwards compatible.
Vague hypothetical future scenarios do not serve as useful evidence. If
the need ever arises for such feature detection to be incorporated into
a future language, we can come back and take another look at the issue
in a future version of the specification.
--
Lachlan
-public-webapi
+public-webapps
Boris Zbarsky wrote:
Lachlan Hunt wrote:
If I add the following paragraph to the security section, would this
adequately address this issue?
If, at any time, the implementation detects a situation which would
violate security policies, the implementation MAY
%20APIproduct=WebAppsWG
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Maciej Stachowiak wrote:
On Jul 14, 2008, at 8:15 AM, Lachlan Hunt wrote:
To avoid forcing implementers to bother implementing such a useless
feature, and potentially lying about their support. Basically, this
should only be for languages other than ECMAScript that don't have
other
Boris Zbarsky wrote:
Lachlan Hunt wrote:
Given that IE, Webkit and Opera seem to be in favour of dropping
NSResolver, if Mozilla will agree, I'm more than happy to do so
OK. We talked it over, and this sounds like the best way going forward
for now.
I have stripped all requirements from
risk).
As the NSResolver has now been removed from the specification, so has
this security requirement. Therefore, I'm closing this issue because
it's no longer relevant.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
-www-style
+public-webapps
Andrew Fedoniouk wrote:
Lachlan Hunt wrote:
Andrew Fedoniouk wrote:
Bert Bos wrote:
(It seems to me you shouldn't need it at all. The problem seems to
be that x.querySelector(:root) doesn't return x. That looks
strange to me: you pass a tree and a pattern
suite with all other functions in the DOM,
which means we should not throw for extra arguments. I see no reason to
treat this function differently than everything else.
OK, agreed. No exceptions for extra arguments.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
NSResolver has been removed, I'm closing this issue.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
)?
Since NSResolver has since been removed from the spec, I'm closing this
issue as it is no longer relevant.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Lachlan Hunt wrote:
Boris Zbarsky wrote:
* I don't see any indication of what the language bindings for this
IDL should look like in languages which do not support function
overloading based on number of arguments and do not allow functions
with variable numbers of arguments. If it has been
that it detects is
non-conforming?
Since NSResolver has since been removed from the spec, I'm closing this
issue as it is no longer relevant.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Lachlan Hunt wrote:
It's been suggested to me that the spec should say something about
support for the other methods that use feature strings, including:
interface DOMImplementationSource {
DOMImplementation getDOMImplementation(in DOMString features);
DOMImplementationList
at the F2F last week.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
in the current editor's draft. Though I'd
rather not make too many additional changes now as I don't want to hold
up publication. Any other issues like this can wait till after this
Last Call draft is published and can be fixed before it goes to CR.
--
Lachlan Hunt - Opera Software
http://lachy.id.au
.org/Archives/Public/public-webapps/2008OctDec/0216.html
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
during this next LC period.
* s/an an asterisk/an asterisk/ in section 6.1.
Fixed.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
the NodeList instances returned were
still static lists.
Please let me know whether or not you are satisified with this response.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
with this response.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
an additional
example with them reversed.
You can review the changes in the latest editor's draft.
http://dev.w3.org/2006/webapi/selectors-api/
Please let me know whether or not you are satisfied with this response.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
versions of each of the 4 major browsers, changing
the name at this stage is not possible.
Please let me know whether or not you are satisfied with this response.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
inefficient if we had to construct
the entire node list at NodeList construction time, too.
We are not changing the behaviour of all NodeLists, just reusing the
same interface for both static and dynamic lists.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
to make on this document.
Great, thanks.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Cameron McCormack wrote:
Lachlan Hunt:
It seems from the Java bindings section of Web IDL that the way to
define modules and how they're mapped to Java packages isn't yet very
stable.
I’ve added a way to specify the Java package naming method now:
http://dev.w3.org/2006/webapi/WebIDL
:scope would be useful
in a matchesSelector() function, we can investigate solutions to address
the issue.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Sean Hogan wrote:
Lachlan Hunt wrote:
Sean Hogan wrote:
Gregory Reimer (the author of reglib) points out that
Element.matchesSelector would be useful for event delegation.
See http://blogs.sun.com/greimer/entry/opera_10_will_suport_selector
It would also neatly tie in with NodeFilter in DOM
changed the heading to Informative References.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Doug Schepers wrote:
Hi, Lachlan-
Lachlan Hunt wrote (on 12/8/08 11:26 AM):
Selectors are evaluated against a given element in the context the
entire DOM tree in which the element is located.
...in the context of?
I'm not sure how to phrase that any more clearly. It means that when
Simon Pieters wrote:
On Mon, 08 Dec 2008 17:26:18 +0100, Lachlan Hunt
[EMAIL PROTECTED] wrote:
== Section 6. The NodeSelector Interface
The caller must pass a valid group of selectors.
That's an authoring requirement, explain how that is applicable?
It seems perfectly applicable
Sean Hogan wrote:
Lachlan Hunt wrote:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5865
Current implementations:
http://base2.googlecode.com/svn/doc/base2.html#/doc/!base2.DOM.Element.matchesSelector
http://developer.yahoo.com/yui/docs/YAHOO.util.Selector.html
http://www.prototypejs.org
the Interoperability Consideration section to more
accurately reflect the result of different levels of Selector support
and offer advice for dealing with it.
http://dev.w3.org/2006/webapi/selectors-api/#interoperability
Please let me know if you are satisfied with this repsonse.
--
Lachlan Hunt - Opera
and :first-letter). So this note may need correction.
As Boris explained, this is not relevant.
You may review the changes in the latest editor's draft.
http://dev.w3.org/2006/webapi/selectors-api/
Please let me know if you are satisifed with this response.
--
Lachlan Hunt - Opera Software
http
Lachlan Hunt wrote:
Erik Dahlström wrote:
On Mon, 08 Dec 2008 17:26:18 +0100, Lachlan Hunt
lachlan.h...@lachy.id.au wrote:
== 8. Examples
Please add an example such as this one:
...
Then explain how to use the Selectors API to select only the svg
'font' elements and how to select only
to see.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
the ones affecting JS libraries the most today, are likely to be addressed.
[1]
http://www.w3.org/Bugs/Public/buglist.cgi?product=WebAppsWGcomponent=Selectors+API
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
address it, I will certainly try and do so.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
.
It would really help a lot if those who believe being able to resolve
namespaces is an important feature, could document clear use cases that
cannot be solved easily without, or would be solved more easily with,
support for namespaces.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http
it will be to evaluate them and find an appropriate solution.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
that are
trivial to make up.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
the element itself, and as your example shows, doing so would be
pointless and confusing.
I've just spotted one more issue:
definitions of the querySelector methods
Is the plural intended?
Yes, there are two definitions. One for querySelector() and another for
querySelectorAll().
--
Lachlan
?) that it intends to benefit. This will then allow me to more
easily evaluate and potentially tweak the proposal when it comes.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
that involve normalization.
I do not understand that claim because, since Selectors currently
doesn't require normalisation, any test cases that relied on
normalisation would be invalid tests.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
methods of the NodeSelector interface.
Please let me know if you are satisfied with this response. You can
review the changes in the latest editor's draft.
http://dev.w3.org/2006/webapi/selectors-api/
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Resig's tests [1], into the test suite.
I started writing one [2], but it's not yet finished. I will be making
time to work on it very soon, as it has now become a priority.
[1] http://ejohn.org/apps/selectortest/
[2] http://dev.w3.org/cvsweb/2006/webapi/selectors-api-testsuite/
--
Lachlan
-normative note?
The entire example section is already non-normative.
excluding all others, requires an additional processing to filter the result.
requires additional processing, or an additional step
Fixed.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
on
whether or not we could or would make the change.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Jonas Sicking wrote:
On Fri, Feb 13, 2009 at 5:23 AM, Lachlan Hunt lachlan.h...@lachy.id.au wrote:
e.g.
function nsresolver(ns) {
uri = {xht: http://www.w3.org/1999/xhtml;,
svg: http://www.w3.org/2000/svg}
return uri[ns];
}
For resolving the default namespace, this would return
is the correct behaviour or not.
It seems like something WebIDL should define, but I couldn't find
anything in the spec on the issue.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
-357
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Alexey Proskuryakov wrote:
12.03.2009, в 17:19, Lachlan Hunt написал(а):
WebKit has a bug with the |foo selector.
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/28
Opera and Firefox pass
This is actually a difference in createElementNS(null, p) vs.
createElementNS(, p
-storage-key
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
/2009JanMar/0585.html
http://lists.w3.org/Archives/Public/public-webapps/2009JanMar/0586.html
I will work in John Resig to get those tests integrated into the test
suite soon.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
CR relatively
quickly. If we need to wait for at least 2 implementations that both
get 100%, that will just delay the spec by 6 to 12 months awaiting the
browser vendors' next release cycle.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
/public-webapps/2009JanMar/0788.html
[4] http://www.hixie.ch/tests/adhoc/dom/selectors/001.html
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Boris Zbarsky wrote:
Lachlan Hunt wrote:
I've also begun to add tests for the namespace selector syntax [2] to
the second set, but they are currently a work in progress and are not
functioning properly. If anyone can figure out what I've done wrong,
please let me know.
I'm glad to try
Hi,
The spec currently requires the first 2 callbacks for the
changeVersion method, while the 3rd is optional. The spec should make
all of the callbacks optional so authors don't resort to specifying
empty functions when they don't actually need to do anything with it.
--
Lachlan Hunt
/webdatabase/#processing-model
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
in the transaction are discarded.
Can you clarify this statement so that it's clearer that it's referring
to the transaction's error callback, and not a statement error callback
in executeSql.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
and evaluate the problems being solved, and determine if it's
really worth addressing in this version.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
target element matches a given selector. So it
would be something like:
if (evt.target.matchesSelector(.fooinput.bar)) {
...
}
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
().
It was discussed a couple of days ago in IRC. It's based on the
functionality provided and needed by javascript libraries.
Garrett Smith wrote:
Lachlan Hunt wrote:
div2.matchesSelector(:scope~div, div1);
The matching seems backwards. Should be on the matcher, instead of the
element? I don't
Lachlan Hunt wrote:
Sean Hogan wrote:
I think a couple of those features are pretty low priority:
- I don't see the point of collective queries on NodeLists.
Are there any references for the proposal?
Otherwise I can't think of any useful queries that can't already be
achieved with a single
it tries
to create it. Otherwise, it will be valid.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
via querySelector*() or getElementsBy*(), or wherever else.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
until we can create arbitrary NodeLists.
It would simplify the issues that John described in his last e-mail, but
the exact use cases aren't entirely clear which is making finding and
determining the most appropriate solution difficult. I'm hoping John
can answer this question.
--
Lachlan Hunt
of elements can be
provided somehow and that the implementation can execute the query on
each distinct element in that collection. How exactly that is done is
just an API design issue.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
easier to define, but
otherwise, no normative changes.
I also fixed up the IDL for the NodeSelector interface to match the
current WebIDL requirements. I made these changes to the level 1 spec too.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
used once.
I'm not sure which alternative would be best, and I'm kind of hoping
there's a 4th alternative I haven't thought of yet that can address the
use cases easliy enough.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
for the cases where they're
using custom pseudo-classes not supported by the browser)
One possible modification I'm considering is introducing a separate
factory method for creating implied scope selectors:
createScopedSelector(selector); rather than using a boolean parameter.
--
Lachlan Hunt
or not such a use case is significant. It seems more natural to want to
restrict the results to those within the same tree.
See the current editors draft for more details.
http://dev.w3.org/2006/webapi/selectors-api2/
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Boris Zbarsky wrote:
On 9/26/09 4:36 PM, Lachlan Hunt wrote:
A scoped selector string is a string that begins with an exclamation
point followed by a the remainder of the selector.
This assumes that '!' will never be allowed at the beginning of a CSS
selector, right?
It does
a
selector like em as being equivalent to :referenceem.
I also defined the :reference pseudo class in the spec (formerly known
as :scope in previous discussions) to match the contextual reference
elements.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
.
[1] http://dev.w3.org/2006/webapi/selectors-api2/
[2]
http://www.w3.org/Bugs/Public/buglist.cgi?product=WebAppsWGcomponent=Selectors%20API
[3] http://lists.w3.org/Archives/Public/public-webapps/2009JulSep/1198.html
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
~/2006/webapi/selectors-api/Overview.html?rev=1.101content-type=text/html;%20charset=UTF-8
I'll make all the necessary editorial changes to get it ready for CR
when I find out what the publication date will be.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Lachlan Hunt wrote:
I have now split the test suite up into 3 files, similar to how I
prevoiusly described [1]:
1. Baseline Tests: HTML with CSS Level 2.1 Selectors.
2. Additional Tests: HTML with Selectors Level 3.
3. Additional Tests: XHTML+SVG with Selectors Level 3.
http://dev.w3.org/2006
.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
.org/Archives/Public/public-webapps/2009AprJun/1221.html
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
selector would work fine?
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Lachlan Hunt wrote:
There must be at least two complete, independent implementations, each
of which must pass 100% of the baseline testsuite and should pass
additional tests, dependent on the following conditions:
...
The current state of implementations is as follows:
Minefield:
Baseline
Boris Zbarsky wrote:
On 11/26/09 9:58 AM, Lachlan Hunt wrote:
Actually, correction. Minefield and Opera don't meet the condition if we
keep the shipping requirement in the exit criteria.
Which imo we should. I don't think we want to be opening up that loophole.
The Gecko 1.9.2 branch builds
don't actually try to implement the
methods themselves. They just implement somewhat compatible
functionality and expose it on their own objects (e.g. $(divp);
instead of document.querySelector(divp);).
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Robin Berjon wrote:
On Nov 26, 2009, at 15:07 , Lachlan Hunt wrote:
Jonathan Watt wrote:
Nevertheless, that doesn't mean that Web content shouldn't be
able to process XML that uses xml:id using script and present the
processed information to the user using content and semantics
that *does
help if you
could find some other APIs and illustrate with some real world sites
that use them, where namespace-supporting APIs are utilised for good
reasons on the client side.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Mozilla and WebKit have begun their implementation of matchesSelector,
which is defined in it.
The editor's draft is here.
http://dev.w3.org/2006/webapi/selectors-api2/
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Sean Hogan wrote:
On 8/01/10 1:19 AM, Lachlan Hunt wrote:
can we publish Selectors API Level 2 as an FPWD?
http://dev.w3.org/2006/webapi/selectors-api2/
FYI, it seems the whole Status of this Document hasn't been updated for
Selectors-API2.
Yeah, that will get fixed up when I get the spec
points to, and then follows the normal rules for evaluating
querySelector. Given that selector, any descendents of refNode that are
also descendents of element (the context node) will be matched, the
first of which will be returned.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http
to:
document.querySelectorAll(:scope+p, elm);
Anyway, since the CfC for FPWD has already begun, I'd rather not make
any major changes till afterwards. I'd also like to hear from a few
other people on this issue.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
/0317.html
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
interoperability by
standardising this? Are these icons meant to be used by web content, or
meant only for internal use by the browser?
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
. It seems much more likely that developers would want to
have all icons used to be designed with a common style.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
?html;32 or about:icon?ext=htmlsize=32
(though, I think being shorter and avoiding '' is better, so authors
don't have to bother escaping it in their HTML)
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
/2006/webapi/selectors-api-testsuite/
[2] http://lists.w3.org/Archives/Public/public-webapps/2009AprJun/1221.html
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
, though I'm not sure why. So I would
like to get clarification whether that is in fact the case, and whether
[NoInterfaceObject] really is what I should be using here.
[1] http://lists.w3.org/Archives/Public/public-web-perf/2011Mar/0058.html
--
Lachlan Hunt - Opera Software
http://lachy.id.au
://bugzilla.mozilla.org/show_bug.cgi?id=518003
[2] https://bugs.webkit.org/show_bug.cgi?id=29703
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
On 2011-04-08 18:22, Boris Zbarsky wrote:
On 4/8/11 6:44 AM, Lachlan Hunt wrote:
2. Using the :scope selector in existing implementations will throw a
syntax error.
On which note, it seems like :scope will first show up prefixed as well,
right?
Yes, that's reasonable.
In which case, do we
an exception, or should it just accept
that ref[0] was an element and use that?
For NodeLists, should it accept any NodeList and only use the Element
nodes? e.g. element.childNodes may contain text or comment nodes.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
1 - 100 of 158 matches
Mail list logo
