User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1 Custom namespace element has style '-moz-user-focus: normal': <my:box style="-moz-user-focus: normal"> <xul:description>Hello</description> </my:box> It seems like my:box gets focus but 'focus' and 'blur' events isn't fired and pseudoclass :focus is invalid (styles aren't activated). Reproducible: Always

Bug probably realated with bug 306315.

Alexander, see discussion in bug 256003 and bug 250006. So I tried to use tabindex="1" for the custum namespaced element, but that doesn't seem to work. When I look at bug 250006, comment 7 and the next comment there, that seems to be deliberate. But that would mean there is now way anymore to focus a randomly namespaced element, which is a bad thing, not?

(In reply to comment #4) > But that would mean there is now way anymore to focus a randomly namespaced > element, which is a bad thing, not? I belive it's bad thing. > Alexander, see discussion in bug 256003 and bug 250006. > So I tried to use tabindex="1" for the custum namespaced element, but that > doesn't seem to work. When I look at bug 250006, comment 7 and the next comment > there, that seems to be deliberate. Removing '-moz-user-focus' for xhmtl looks strange for me. I don't understand why should each xml based languague have own behaviour to work with focus. In particular why should xul and xhmtl have? Why can't taborder method and '-moz-user-focus' live together in xhtml? (It seems to me taborder and '-moz-user-focus' live together in xul successfuly). There is user-focus style on w3c working draft css3. When working draft will become specification then this style will be ignored too?

User-focus has been removed from the draft, afaik ( http://lists.w3.org/Archives/Public/www-style/2002Jul/0152 ). I think (not sure though) the intent is also to remove -moz-user-focus support for xul. So eventually, everything should be done with tabindex. But it sure would be nice if tabindex could also be used somehow with a random namespaced xml element.

I don't think we want to support -moz-user-focus for anything at all.... if we can drop support for XUL and move to a non-CSS-based system, that would be great too. Being focusable is really a behavioral concept, not a presentational one. I suggest we wontfix this.

(In reply to comment #7) > I don't think we want to support -moz-user-focus for anything at all.... if we > can drop support for XUL and move to a non-CSS-based system, that would be > great too. Being focusable is really a behavioral concept, not a > presentational one. > > I suggest we wontfix this. > If "-moz-user-focus" is moved at all then it's ok for me (btw, is there a bug for XUL support droping?). Does @tabindex work for random namespaced element?

The last CSS WG meeting I went to was at the Feb 2006 plenary. It was said that since people are defining their widgets in CSS, it would be a convenient place to define focusability. No one at that meeting disagreed, but I have heard Boris' comment from others since then. Basically, it's still unknown if CSS will support user-focus or something like it in the future. We can't force all markup languages to support tabindex either. So we need some solution for focusability of custom namespaced elements now. I personally have no problem with support -moz-user-focus until something better comes along and we deprecate that generally.

Mass un-assigning bugs assigned to Aaron.