This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 20925 - "The protocol attribute must run these steps: "
Summary: "The protocol attribute must run these steps: "
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: URL (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+urlspec
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-09 01:38 UTC by Ian 'Hixie' Hickson
Modified: 2014-10-14 17:57 UTC (History)
2 users (show)

See Also:

Attachments

Description Ian 'Hixie' Hickson 2013-02-09 01:38:37 UTC 
http://url.spec.whatwg.org/#interface-urlutils

"The protocol attribute must run these steps:"

I assume that is missing an "on getting" or some such. Same applies to the others.
Comment 1 Anne 2013-02-12 09:49:33 UTC 
It's kind of intentional and this is by far not the only place this criticism would apply. Maybe it's time to change this though.
Comment 2 Anne 2014-05-22 10:31:32 UTC 
Domenic, are you planning on encouraging a style for attribute/method definitions down the road?

I'm tempted to hold of fixing this until IDL is revised to be more clear about data properties vs getters/setters, etc.
Comment 3 Domenic Denicola 2014-05-22 12:27:54 UTC 
That seems like a good idea, although I agree with Hixie that a quick clarification would be good in the meantime.

I am also not sure how important encouraging such stylistic clarifications are? I mean, yes, it would be nice if everyone followed a template for "on getting, run these steps"; "on setting, run these steps", but you can pretty much understand the existing specs already.

(I think my pipe dream would be that IDL moves away from `attribute x` vs. `readonly attribute x`, instead declaring `get x` and/or `set x` separately, and that the description for `get x()` contains the getter algorithm, and for `set x(value)` contains the setter algorithm. But that's an even bigger ask, again for not too much added value.)
Comment 4 Anne 2014-05-22 12:33:24 UTC 
Yeah, I think that pipe dream is how I'd like to have it too. There's too much disconnect at the moment which is confusing to developers.