canmove, Confirmed users
2,675
edits
(drafted DOM vendor prefixes problem statement, thoughts, simple proposal) |
m (typo) |
||
Line 101: | Line 101: | ||
All standards in development have the challenging seemingly contradictory problems of: | All standards in development have the challenging seemingly contradictory problems of: | ||
# '''needing some implementation to reality-check''' that the API/protocol/format "works" as intended, or is workable/usable | # '''needing some implementation to reality-check''' that the API/protocol/format "works" as intended, or is workable/usable | ||
# '''being stuck with a specific (often buggy) implementation''' once it ships because there's content/pages/apps out there that | # '''being stuck with a specific (often buggy) implementation''' once it ships because there's content/pages/apps out there that depend on it. | ||
There are three areas of the open web app platform that this has been problematic: | There are three areas of the open web app platform that this has been problematic: | ||
Line 158: | Line 158: | ||
Our goal is to establish a convention (like the above) for all such pre-CR DOM APIs that has the consensus of implementers so that we can avoid creating broken versions of APIs | Our goal is to establish a convention (like the above) for all such pre-CR DOM APIs that has the consensus of implementers so that we can avoid creating broken versions of APIs | ||
== Social and Identity == | == Social and Identity == |