Timo Tijhof 4854d644ee doc: Get rid of 'static' property container in jsduck index ... Us grouping the inheritable static properties that way is an implementation detail that is polluting the index and makes it harder to refer to individual identifiers. It also causes problems under JSDuck 5 because that version is more strict about defining properties (Foo.static.bar) of which the parent is not defined in the index (Foo.static), we'd have to add a sea of `@static @property {Object} this.static` all over the place. Might as well hide this implementation detail and just consider them static properties (just like we already do for "private" properties). Change-Id: Ibf2ebf7752aabc2b75b6ac6fa00e2284a181a600		2013-11-19 10:21:39 +00:00
..
ce	Rename this.$ to this.$element, and this.$$ to this.$	2013-11-03 23:03:49 -08:00
dm	doc: Get rid of 'static' property container in jsduck index	2013-11-19 10:21:39 +00:00
init	Combine all the saveError.* track events	2013-11-19 11:02:52 +05:30
test	[browser test] Additional UTF-8 editing test string	2013-11-13 18:46:44 +00:00
ui	Only replace meta-data from dialog if it has changed	2013-11-18 14:13:15 +05:30