Bug 76811
| Summary: | Drop support for WebSocket and EventSource .URL | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Simon Pieters (:zcorpan) <zcorpan> |
| Component: | WebCore JavaScript | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | abarth, adam.bergkvist, annevk, ap, dglazkov, ian, mike, Ms2ger, pf, ukai, webkit.review.bot, yutak |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Simon Pieters (:zcorpan)
+++ This bug was initially created as a clone of Bug #40899 +++
.URL was renamed to .url in the specs. You implemented both. .URL should be dropped. If .URL continues to be supported, content may be authored that relies on it existing, which means it will be harder for you to remove it the later you remove it, and will cause incompatibility problems for other browsers.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
It's just a mistake in the specs that URL got renamed to url. Totally inconsistent and unhelpful, given that this happened after implementations shipped based on earlier spec versions.
Ms2ger (he/him; ⌚ UTC+1/+2)
Then you should have complained at the time, not implemented both. That's just harmful to all of us, and frankly irresponsible.
Alexey Proskuryakov
Complain like this <http://lists.w3.org/Archives/Public/public-webapps/2010AprJun/1129.html>?
Simon Pieters (:zcorpan)
Yes. Had you complained a bit earlier, maybe we would have got our way (I also preferred "URL" at first, but didn't get any backup except from Hixie). I then gave in and Opera switched to "url", and the spec changed. *Then* you complained, but evidently it wasn't persuasive enough (or it was too late) to convince us or Mozilla to change back, so "url" is what it is.
http://lists.w3.org/Archives/Public/public-webapps/2010AprJun/0332.html
http://lists.w3.org/Archives/Public/public-webapps/2010AprJun/0563.html
Anne van Kesteren
Bug 248787 and bug 248781 took care of this.