Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
What version of the HTML spec was the tag added?
Tables were not in HTML 2 but were in HTML 3.2.
(There were no, non-draft, specifications between those two versions, but HTML 3.0 also included tables.)
HTML 3.2 allows tables for layout but warns that there may be undesired side effects.
can be used to markup tabular material or for layout purposes. Note that the latter role typically causes problems when rending to speech or to text only user agents
HTML 4 removed that option:
should not be used purely as a means to layout document content
… and introduced support for stylesheets. (NB: The "divs vs tables" question is usually better expressed as "stylesheets vs tables").
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
Just came across a project that had custom-made tags.
Something like:
<buildings>
<building-1></building-1>
<building-2></building-2>
</buildings>
(This code doesn't do anything; it's an example)
(It's not mine) (https://codepen.io/perbyhring/pen/jpQwav) What is the use of this?
Those custom HTML elements have been introduced some time ago and should make HTML code more readable.
"Those elements provide a way to build own DOM elements but also have some drawbacks as simply defining and using an element called blue-button does not mean that the elements represent a button. Tools such as Web browsers, search engines, or accessibility technology will not automatically treat the resulting element as a button just based on its defined name."
Read more about them in the html standard.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
Why some HTML elements like: radio buttons, check boxes, datalists... aren't styleable? I mean ... this is so bad that we have to create a custom element over the standard element so we can style it Is there any specific reason to that?
I'm not asking for workarounds for these elements, I'm asking WHY they can't be styled natively ... Is there something in the HTML specification that prevents these elements to be styled?
MDN has an explanation:
In the early days of the Web—around 1995—form controls were added to HTML in the HTML 2 specification. Due to the complexity of form widgets, implementors chose to rely on the underlying operating system to manage and render them...... Because users are accustomed to the visual appearance of their respective platforms, browser vendors are reluctant to make form controls stylable"
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
This is a question to mostly satisfy my curiosity: with the growth and acceptance of larger javascript frameworks the last, say, 5 years, it has become increasingly common to have attributes on elements add custom behavior to known html elements. For this reason html5 introduces data-* attributes, which just about every tool, including the browser parsing the dom actively ignores while rendering but are key for Js framework to enrich html as full-fledged application platform.
With Angular directives (for example), app builders enrich html as a whole by adding the ability to even create custom elements. The thing is however, this is where editing tools, like Visual Studio, break, since they like to actively check if the html elements you add exist.
Now, my question is not about visual studio (I know how to disable html validation), but why did the creators of the html5 standard never considered to include data-* elements as well? Or maybe they did, and the idea was discarded somehow. Does anyone know?
The data- prefix is actually part of the HTML5 draft
these attributes are for semantic HTML; as an example, attaching a database ID to an HTML element so that HTML parsers can use this data. In the case of Angular, the custom attributes do not carry data; they extend HTML.
Mozilla has some guidelines on the topic of the data prefix: https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Using_data_attributes
Edit The intent of HTML elements is to carry content to be displayed by the browser, attributes to attach meta-data to these elements and <head> to attach meta-data to the whole document. There are no data- elements in HTML so it's consistent with that design.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
I want to know the HTML and CSS version of a website/webapplication ?
By HTML version I assume you mean the doc type. That can be retrieved using the following line of javascript:
console.log(document.doctype);
CSS, however, doesn't have versions in the sense that a version can be declared in the document. Rather, if a style declaration is supported (i.e, the browser can interpret it) then it gets rendered. Terms like CSS3/CSS2.1/Etc are just names we use to describe the state of accepted style declarations in a given generation. They're not bound to some kind of identifiable version that a browser can explicitly detect.
So the short answer is that CSS version is dictated by the styles you include in your stylesheet, and CSS support is dictated by the browser you use to view your website.
Tools like Modernizr will help you detect what your browser does and does not support.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 9 years ago.
Improve this question
I want to put some information about developer of site and not know how to do it in HTML or with use microdata or note (i.e. schema.org or other).
Can you share some how to put information about developer (I will be partially author, publisher)?
If the developer is not the publisher/creator/editor/author/contributor of the page/content, you cannot use properties of http://schema.org/WebPage nor the Dublin Core vocabulary.
Maybe you could use the properties foaf:made and/or foaf:maker from the FOAF vocabulary. But I’m not sure about it, as they seem to be closely related to dc:creator, which wouldn’t be appropriate. Maybe have a look at foaf:currentProject and foaf:pastProject, too.
The humans.txt could be used to informally note any developers/designers etc.