- From: Ian Hickson <ian@hixie.ch>
- Date: Thu, 1 Jun 2006 19:10:23 +0000 (UTC)
- To: Anne van Kesteren <annevk@opera.com>
- Cc: dev-tech-xbl@lists.mozilla.org, public-appformats@w3.org
On Thu, 1 Jun 2006, Anne van Kesteren wrote: > > > > | > > > > | 5.7.3. The :-xbl-bound-element Pseudo-Class > > > > | > > > > | ISSUE-V Should add a forward reference to section 5.10. > > > > > > > > Why? > > > > > > Because that section explains the "loop effect" with > > > :-xbl-bound-element and :-xbl-binding... > > > > I don't see anything in section 5.10 that mentions > > :-xbl-bound-element. Am I missing something? > > Check the last two paragraphs. They talk about loops (:hover is one > example). This applies to :-xbl-bound-element and -xbl-binding as well. Well, sure, it applies to anything. I don't understand why you would need a link from the pseudo-class to that, though, since the pseudo-class is the last thing anyone would use to apply that property. > > > The basic problem is that listening for specific events is not > > > guarenteed to work cross-platform given that some devices might not > > > dispatch certain events, like some of the mouse events... > > > > Sure, but why is that XBL2's problem? > > Well, the problem applies to more than XBL, fair enough, but pointing such > things out to authors might benefit. Those notes don't have to be normative or > anything... Seems to me these notes would be better placed in the spec that defines the events. There are "gotchas" with XML, HTTP, Unicode, URIs, IRIs, encodings, and all kinds of other technologies that XBL2 relies on, but we're not going to list them all in the XBL spec. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 1 June 2006 19:10:40 UTC