A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.
To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).
Talk:Reviewing: Difference between revisions
(multiple comments: datagrid/fold/tabs, video, canvas, compass, 9-slice, pre/textarea line numbers)
No edit summary
|Line 451:||Line 451:|
Revision as of 11:06, 26 July 2010
Suggest a new tag:
To provide a standardize way to tell tools like html tidy that the code in that section should not be reformatted without an explicit override. It would do nothing in the browser. Some markup is best left as is. For example, tables, embedded structured data, etc.
Whitis 21:51, 6 May 2009 (UTC)
I would recommend asking the developers of the tools you use (e.g. tidy) to support a "class" value that would do this, that way it can work even with HTML4 documents, no need to add an element or anything. Hixie 21:55, 6 May 2009 (UTC)
No good. That would be specific to individual tools. There needs to be a standard used by all tools. If you want to include a standard class instead of a tag, that is fine. But it should be mentioned in the markup spec as that is one document that all the the tool developers will read. This does fall within the domain of the spec, just as providing print media support, handicapped support, etc. View source (or edit) is another presentation.
Consider this a source code accessibility issue. Whitis 07:25, 7 May 2009 (UTC)
4.11.2 datagrid element/folds/tabs Note: this comment and the ones which follow evolved as they were written. Some evolved with parts moving from tags to attributes or to CSS. Some evolved with new names based on finding existing precedent. Some of the changes were backpatched into the text, but not all.
There should also be a <fold> tag (or equivalent functionality) that is very similar but less table/list oriented. <fold status="open">
Attributes might be another way to do this which avoids inserting a tag between body and h2.
<fold_title>Blah blah </fold_title>
Absence of fold attribute makes it unfoldable unless the user allows it.
This is similar to the hidden attribute but with some key differences. A fold Icon would still be present, along with descriptive text. Folding and unfolding would be accomplished by the user agent without any scripts to set the disabled attribute. In the case of sections, there would be special handling in that the text of any H1...H6 tag would not go away when folded. For other contexts, there may need to be a <fold_title>...</fold_title> or similar tag or a fold_title="tagname" attribute that lists what tag contents will be displayed when folded.This can be done in CSS as well. However folds and tabs are a basic logical construct and could exist in both domains. If the basic construct isn't defined at the HTML level, documents will be missing fold/tab titles that can be used by user stylesheets or user controls to override document behavior. Even if new tags/attributes are not defined, the basic markup usingor(or other elements which can also be tabbed or folded) should be mentioned in the HTML5 spec.
I.E. This is how you define where the folds/tabs would occur and this is what to use for a title and CSS is used to make it actually happen. You can not leave this to be fragmented by different folks using different classes. Since class allows multiple classes to be specifified, standard classes could be used while still retaining the ability to style each object individually (or as a subgroup) by specifying multiple classes. HTML5 at least needs to specify the classes to be used and make sure that the classes alone are adequate.Now technically, datagrid allows flow context. It is not at all clear how it handles flow content. The spaces for examples desparately need to be filled in and more examples given (flow content, sections, lists). If you are going to use it like the fold tag/attribute, <section> should be explictly mentioned and an example given, as that is an important case, though not the only one. As should numbered/unnumbered lists and definition lists.
blocks are another important case where folding is reasonably expected. User agents may provide an ability to, at the users request, fold all sections, whether or not they have a fold attribute (it basically sets fold to yes if it exists and creates it if it doesn't. The user agent can also provide an unfold all. This would work for <section> tags but wouldn't work as well for (un)numbered lists as existing content doesn't identify a title to be retained when folded (unless it has a
tag). "The data being presented is provided by script using the methods described in the following sections." No. That probably isn't what you meant to say. It can be provided by a script but it must be possible to provide it without one. The section on datagrids should spell out how you define the nesting levels and initial fold state on grid rows, even if that is described elsewhere. I don't see support for tabs. Maybe I didn't missed it, or maybe it is done using CSS. Tabs in the modern GUI sense. Not to be confused with the obsolete HTML3 tab tag (typewriter tabs) that were replaced with tables. <section tabs="true">
Tab title.... </section> <section>
Tab Title... </section> </section> If the browser doesn't support tabs, it can display the sections in a normal vertical orientation. section should take a title attribute, to be used when there isn't an h1...h6 section title. Another place where tabs are needed is in tables. Consider the tables here which are really subsets of a larger table. http://en.wikipedia.org/wiki/Comparison_of_media_players#Subtitle_support <colgroup tabs="true"> <colgroup title="Tab 1"> ... </colgroup> <colgroup title="Tab 2"> ... </colgroup> </colgroup> Browsers should be encouraged to provide a control that would convert sections or table column groups to tabs. Also to freeze or repeat row/column headings when a table wider/higher than the window scrolls, under user control. And they should provide an untabify control. Tabs may, and often will, occur inside forms. This could be provided via CSS, provided the base HTML contains provisions for a tab title. The same mechanism for titles can be used for both folding and tabbing. Note: looks like <legend> tag could be used for folding/tab titles, with H1...H6 used if not present. Needs to be allowed in <section> and
- . <section><legend>...</legend> ... </section> would be a suitable docbook style replacement for the broken H1...H6 tags. This would make more sense than the <section>
blocks could have a numbering option
sets the initial line number to 100 and activates line numbering. This allows the text which accompanies a
- <fold_title>Blah blah </fold_title>