7776 2009-09-30 16:24:02 +0000 rename appcache events? 2010-12-01 15:30:55 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC Linux VERIFIED INVALID NE P2 normal --- 1 annevk ian ian mike mjs Ms2ger public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 27951 0 annevk 2009-09-30 16:24:02 +0000 The appcache events are not consistent in style. Is is still feasible to introduce changes here and make them more consistent? * obsolete -> obsoleted * updateready -> updated * noupdate -> notupdated This would make these events consistent with cached. progress could be renamed to progressing to be more consistent with similar events though I think it should get a different name altogether as suggested in another bug. 27952 1 annevk 2009-09-30 16:24:21 +0000 Adding NE keyword so other implementors see this. 27994 2 mjs 2009-10-02 06:38:28 +0000 We have implemented these in WebKit. I do not know if they are used. There are definitely mobile sites using the app cache, but I don't have any quantitative data. The suggested new names don't seem sufficiently better to be worth the change. It seems to be standard for DOM events to be named in the present tense instead of the past tense - "click" not "clicked", "load" not "loaded". If anything, "cached" is the odd man out. 28453 3 ian 2009-10-18 11:00:10 +0000 I don't feel comfortable changing these now. Please feel free to escalate this if you disagree.