[Bug 27757] New: [Shadow]: how is the autofocus attribute supposed to be handled?

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27757

Bug ID: 27757
   Summary: [Shadow]: how is the autofocus attribute supposed to
be handled?
   Product: WebAppsWG
   Version: unspecified
  Hardware: PC
OS: All
Status: NEW
  Severity: normal
  Priority: P2
 Component: Component Model
  Assignee: dglaz...@chromium.org
  Reporter: m...@rodneyrehm.de
QA Contact: public-webapps-bugzi...@w3.org
CC: m...@w3.org, public-webapps@w3.org
Blocks: 14978

The section "6.2 Focus Navigation" [1] does not specify how the autofocus
attribute [2] is to be handled if set on an element within a ShadowRoot.

As of now Chrome and Firefox consider all elements at page load, including the
ones in ShadowRoots when looking for an element with autofocus. That, however,
is not the behavior I expected from an encapsulated DOM. What I expected is the
same behavior the dialog element presents in showModal in steps 8 - 10 [3].

[1] http://w3c.github.io/webcomponents/spec/shadow/#focus-navigation
[2]
http://www.w3.org/html/wg/drafts/html/master/forms.html#autofocusing-a-form-control:-the-autofocus-attribute
[3]
http://www.w3.org/html/wg/drafts/html/master/interactive-elements.html#dom-dialog-showmodal

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 27751] New: [Custom]: suggest note on requirements

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27751

Bug ID: 27751
   Summary: [Custom]: suggest note on requirements
   Product: WebAppsWG
   Version: unspecified
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: normal
  Priority: P2
 Component: Component Model
  Assignee: dglaz...@chromium.org
  Reporter: faulkner.st...@gmail.com
QA Contact: public-webapps-bugzi...@w3.org
CC: m...@w3.org, public-webapps@w3.org
Blocks: 14968

"The custom element type identifies a custom element interface and is a
sequence of characters that must match the NCName production, must contain a
U+002D HYPHEN-MINUS character, and must not contain any uppercase ASCII
letters. The custom element type must not be one of the following values:"

Would be good to have a note for web devs on why these are requirements

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Re: custom elements without the dash

[Steve Faulkner]

yeah, it was just explained to me by Mike Smith:
"standard custom-elements APIs is that the API doesn’t allow them register
custom elements without a dash"

which I did not know :-)

--

Regards

SteveF
HTML 5.1 

On 5 January 2015 at 14:10, Anne van Kesteren  wrote:

> On Mon, Jan 5, 2015 at 3:03 PM, Steve Faulkner 
> wrote:
> > I understand why, its the zillions of developers out there who don't or
> > don't care, either they are given good reasons not to do it in language
> they
> > understand and is meaningful to them or they ignore requirement and it
> > becomes useless.
>
> If they ignore the requirement they don't get custom elements...
>
>
> --
> https://annevankesteren.nl/
>

Re: custom elements without the dash

[Anne van Kesteren]

On Mon, Jan 5, 2015 at 3:03 PM, Steve Faulkner  wrote:
> I understand why, its the zillions of developers out there who don't or
> don't care, either they are given good reasons not to do it in language they
> understand and is meaningful to them or they ignore requirement and it
> becomes useless.

If they ignore the requirement they don't get custom elements...


-- 
https://annevankesteren.nl/

Re: custom elements without the dash

[Steve Faulkner]

On 5 January 2015 at 13:59, Jirka Kosek  wrote:

> Since there are no namespaces (in XML sense) in HTML language prefixes
> are used instead as a mechanism to prevent clash with future
> standardized element names.
>

I understand why, its the zillions of developers out there who don't or
don't care, either they are given good reasons not to do it in language
they understand and is meaningful to them or they ignore requirement and it
becomes useless.

--

Regards

SteveF

Re: custom elements without the dash

[Jirka Kosek]

On 5.1.2015 14:42, Steve Faulkner wrote:
> Suggest the reasons for not doing so need to be better articulated.

Since there are no namespaces (in XML sense) in HTML language prefixes
are used instead as a mechanism to prevent clash with future
standardized element names.

Jirka

-- 
--
  Jirka Kosek  e-mail: ji...@kosek.cz  http://xmlguru.cz
--
 Professional XML and Web consulting and training services
DocBook/DITA customization, custom XSLT/XSL-FO document processing
--
 OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep.
--
Bringing you XML Prague conferencehttp://xmlprague.cz
--



signature.asc
Description: OpenPGP digital signature

Re: custom elements without the dash

[Steve Faulkner]

>
> It's already mentioned in that Twitter thread. If somebody created
>  we could then never standardize an element using that name.


Sure, but that's not a possibility that has any immediate effect upon a
developer, as I said I suggest the consequences of doing so need to be
better articulated (in the spec?).

--

Regards

SteveF
HTML 5.1 

On 5 January 2015 at 13:51, Anne van Kesteren  wrote:

> On Mon, Jan 5, 2015 at 2:42 PM, Steve Faulkner 
> wrote:
> > Why force hyphen in custom elements?
>
> It's already mentioned in that Twitter thread. If somebody created
>  we could then never standardize an element using that name.
>
>
> --
> https://annevankesteren.nl/
>

Re: custom elements without the dash

[Anne van Kesteren]

On Mon, Jan 5, 2015 at 2:42 PM, Steve Faulkner  wrote:
> Why force hyphen in custom elements?

It's already mentioned in that Twitter thread. If somebody created
 we could then never standardize an element using that name.


-- 
https://annevankesteren.nl/

custom elements without the dash

[Steve Faulkner]

brought up on a twitter thread
https://twitter.com/johnslegers/status/552064145399767040

Why force hyphen in custom elements? See alternative approach at http://
mdo.github.io/mdoml/   and https://
github.com/mdo/mdoml/issues/7 … .

NOTE I am not advocating this approach.

There is no apparent downside for a developer if they do


instead of


claimed issues with use of dash:

(1) causes bloat, (2) reduces readability & (3) reduces flexibility

As there is no perceived negative effect for the developer when using non
dash custom elements (other than opprobrium from the  standards overlords)

Suggest the reasons for not doing so need to be better articulated.
--

Regards

SteveF

[Bug 25813] [Custom]: Throw Exception when EXTENDS and PROTOTYPE have a mismatch

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25813

Anne  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||ann...@annevk.nl
 Resolution|--- |WONTFIX

-- 
You are receiving this mail because:
You are on the CC list for the bug.