[Bug 26425] Drop the default for [Exposed]

# bugzilla at jessica.w3.org (8 months ago)

www.w3.org/Bugs/Public/show_bug.cgi?id=26425

Tobie Langel tobie.langel@gmail.com changed:

       What    |Removed                     |Added

     Resolution|---                         |WONTFIX
         Status|NEW                         |RESOLVED

--- Comment #1 from Tobie Langel tobie.langel@gmail.com ---

I agree on principle, but that ship has sailed.

How would we distinguish between an interface that shouldn't be exposed because [exposed] is missing from an interface that should be because it was spec'ed before we made this change?

Contact us to advertise here
# bugzilla at jessica.w3.org (8 months ago)

www.w3.org/Bugs/Public/show_bug.cgi?id=26425

Boris Zbarsky bzbarsky@mit.edu changed:

       What    |Removed                     |Added

             CC|                            |bzbarsky@mit.edu

--- Comment #2 from Boris Zbarsky bzbarsky@mit.edu ---

We'd distinguish by going and editing every single spec accordingly...

# bugzilla at jessica.w3.org (8 months ago)

www.w3.org/Bugs/Public/show_bug.cgi?id=26425

--- Comment #3 from Tobie Langel tobie.langel@gmail.com --- (In reply to Boris Zbarsky from comment #2)

We'd distinguish by going and editing every single spec accordingly...

Sure. Seems like a lot of work for something that appears to be essentially cosmetics, though. Or am I missing the broader picture?

# bugzilla at jessica.w3.org (8 months ago)

www.w3.org/Bugs/Public/show_bug.cgi?id=26425

Anne annevk@annevk.nl changed:

       What    |Removed                     |Added

         Status|RESOLVED                    |REOPENED
     Resolution|WONTFIX                     |---
             CC|                            |annevk@annevk.nl

--- Comment #4 from Anne annevk@annevk.nl ---

Yeah, the problem is that specifications don't consider workers, or service workers, etc. Not having a default would require specifications to consider what they're doing, which I think is what we want. (There's also been some confusion from developers in the past as to how interfaces end up being exposed. There being an explicit syntax link would help with that too.)

# bugzilla at jessica.w3.org (8 months ago)

www.w3.org/Bugs/Public/show_bug.cgi?id=26425

--- Comment #5 from Tobie Langel tobie.langel@gmail.com ---

OK, that makes sense. We need a strategy to make every spec fix their this though.

# bugzilla at jessica.w3.org (8 months ago)

www.w3.org/Bugs/Public/show_bug.cgi?id=26425

--- Comment #6 from Jeffrey Yasskin jyasskin@gmail.com ---

Making an interface without [Exposed] into a bikeshed and respec error would catch a good fraction of maintained specs.

# bugzilla at jessica.w3.org (8 months ago)

www.w3.org/Bugs/Public/show_bug.cgi?id=26425

--- Comment #7 from Boris Zbarsky bzbarsky@mit.edu ---

And once those get updated, we can change browser IDL parsers and file bugs on any remaining specs that this catches....

# bugzilla at jessica.w3.org (8 months ago)

www.w3.org/Bugs/Public/show_bug.cgi?id=26425

Tab Atkins Jr. jackalmage@gmail.com changed:

       What    |Removed                     |Added

             CC|                            |jackalmage@gmail.com

--- Comment #8 from Tab Atkins Jr. jackalmage@gmail.com ---

Is there a good doc I can point to somewhere in Bikeshed's error message letting people know how to fix things correctly? (I'm not willing to add errors where the solution is "ask someone in #whatwg what to do".)

# bugzilla at jessica.w3.org (8 months ago)

www.w3.org/Bugs/Public/show_bug.cgi?id=26425

--- Comment #9 from Tobie Langel tobie.langel@gmail.com --- (In reply to Tab Atkins Jr. from comment #8)

Is there a good doc I can point to somewhere in Bikeshed's error message letting people know how to fix things correctly? (I'm not willing to add errors where the solution is "ask someone in #whatwg what to do".)

I'll add documentation in WebIDL itself once we get to this and will coordinate with you.

# bugzilla at jessica.w3.org (8 months ago)

www.w3.org/Bugs/Public/show_bug.cgi?id=26425

Jeffrey Yasskin jyasskin@gmail.com changed:

       What    |Removed                     |Added

             CC|                            |jyasskin@gmail.com

--- Comment #10 from Jeffrey Yasskin jyasskin@gmail.com ---

I've filed w3ctag/design-principles#35 to hold the design advice Tab's looking for.

# bugzilla at jessica.w3.org (2 days ago)

Want more features?

Request early access to our private beta of readable email premium.