This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The "previous 25" and "next 25" links are broken when viewing a property for which there isn't a page created yet. Examples: * special property: http://docs.webplatform.org/wiki/Property:Has_type * normal property: http://docs.webplatform.org/wiki/Property:Path A workaround is to strip "&action=edit&redlink=1" from the URL after clicking a red link. The fix is to create a page for the property, I confirmed this by creating http://docs.webplatform.org/wiki/Property:Has_improper_value_for after which the links worked correctly. I will create a small page for every Property.
Relevant properties done. Some remarks for Alex: * Property:Image - rarely used, mostly SVG articles, even assigned with old := Syntax * Property:Is_parameter_for - only contains some bogus pages (srsly, where did it get those pound signs from) * Property:Is_return_value_for, Property:Is_property_of, Property:Has_method_type, Property:Has_object, Property:Has_summary, Property:Has_syntax, Property:Has_description, Property:Has_name, Property:See_also_javascript_method - again with Date, are those needed for something? * Property:Path - is that used? * Property:CSS_object_model_property - not filled by pages, the ones that did provided inconsistent values * Property:css/selectors/pseudo-elements/ - some pages tried to link to [[css/selectors/pseudo-elements/::after]] etc. * Property:Applies_To - unused / inconsistent; although there's Property:Applies_to, that's css specific though as it seems * Property:Language - only used by Form:data_type (Category:Data_Type = only 2 articles) * some erroneous properties were fixed by correctly casing them
(In reply to comment #1) > Relevant properties done. Some remarks for Alex: > > * Property:Image - rarely used, mostly SVG articles, even assigned with old > := Syntax > * Property:Is_parameter_for - only contains some bogus pages (srsly, where > did it get those pound signs from) Do you have some examples of where these are used? > * Property:Is_return_value_for, Property:Is_property_of, > Property:Has_method_type, Property:Has_object, Property:Has_summary, > Property:Has_syntax, Property:Has_description, Property:Has_name, > Property:See_also_javascript_method - again with Date, are those needed for > something? Where are these used? > * Property:Path - is that used? It's going to be used quite a bit on the API_Listing pages to select sub-pages. It's a workaround for a limitation in SMW query syntax. > * Property:CSS_object_model_property - not filled by pages, the ones that > did provided inconsistent values Where is this one coming from? > * Property:css/selectors/pseudo-elements/ - some pages tried to link to > [[css/selectors/pseudo-elements/::after]] etc. ?? > * Property:Applies_To - unused / inconsistent; although there's > Property:Applies_to, that's css specific though as it seems > * Property:Language - only used by Form:data_type (Category:Data_Type = only > 2 articles) > * some erroneous properties were fixed by correctly casing them Thanks so much for looking into this!!
Just go to a property's page to see where it's used, e.g. http://docs.webplatform.org/wiki/Property:Is_parameter_for You created Property:CSS_object_model_property as a string property, it's the "CSS Object Model Property" field on Form:CSS_Property which is passed to Template:CSS_Property. Property:css/selectors/pseudo-elements/ (http://docs.webplatform.org/wiki/Property:css/selectors/pseudo-elements/) came to existence because some pages tried to link to "css/selectors/pseudo-elements/::after" etc., but that got interpreted by SMW due to the double-colon.