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"
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 8 years ago.
Improve this question
Is it bad practice to occasionally put some CSS directly into some HTML tags if I am sure that it won't be used again?
For instance:
<div style="padding-left: 0"></div>
Or do I have to systematically create new class even for little tweaks that will pollute my CSS file?
Yes it is fine. Stylesheets are used mostly to style multiple pages in the same manner and for easier editing. Putting css directly in html also overrides all other conflicting styles.
There is a Programmers Stack Exchange site that's a better fit for questions like this.
Here are two existing questions there that cover this particular topic:
https://softwareengineering.stackexchange.com/questions/138538/is-it-a-bad-practice-to-use-inline-styling-with-generated-code
https://softwareengineering.stackexchange.com/questions/125893/when-should-i-use-a-css-class-over-inline-styling
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").
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 9 years ago.
Improve this question
A perfect example is stackoverflow. When a user types a question, the textarea give the user basic formatting options such as bullet points, numbering, italicize, etc. How can I create a similar textarea? I am currently using html, css and php.
You can use javascript (or more effectively jQuery) to create your own textarea with this behaviour, or look at an existing package such as TinyMCE and configure it to meet your requirements (the approach I would suggest): http://www.tinymce.com/
Easiest way would be to use an editor like TinyMCE: http://www.tinymce.com/
There are others as well, but TinyMCE is what I see used most.
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.