w3c

What is the point of using W3C valid badges? [closed]

由 感情迁移 提交于 2019-12-05 04:55:21
I'm talking about these . Yeah, I know they are intended to show that the page conforms to the standards and should link to page revalidation service. Ok. But why should I as a regular user bother with this? As a visitor I'm indifferent to whether the page is strict XHTML or not, whether it contains dirty IE hacks or not. It is important that a page renders correctly, is convenient and works fast. That's all! And in reality, in many cases these requirements don't get along with W3C standards smoothly. So what is the mania to add something targeted toward developers to a product face? Am I

Detect Printer's Page Size in CSS or JavaScript

由 余生颓废 提交于 2019-12-05 03:38:53
问题 Question Summary: I want to be able to detect a user's printer's page size so that I can send a different page layout based on printer's page size. Example Use Case: Our users are businesses. Some user's want to print basic receipts (and so they have small printers) and some users want to print invoices (i.e. normal 8" * 11" pages). Based on the printer's page size we can recognize what format should be sent to the printer. CSS Specification: Ideally there would be a CSS media setting for

What's the point of Content-Script-Type and Content-Style-Type

由 ⅰ亾dé卋堺 提交于 2019-12-04 23:30:52
问题 Consider these two lines: <meta http-equiv="Content-Script-Type" content="text/javascript" /> <meta http-equiv="Content-Style-Type" content="text/css" /> From the W3's documentation on Scripting, in the section The default scripting language: Authors should specify the default scripting language for all scripts in a document by including the following META declaration in the HEAD Yet it continues in Local declaration of a scripting language to say: The type attribute must be specified for

Can another tag be inside a HTML 5 heading (i.e. h1, h2, h3, etc…)?

由 耗尽温柔 提交于 2019-12-04 22:37:51
I'm not sure about the convention regarding headings in HTML 5 but I wanted to know if I could add a <small> in a <h3> , like this (this could apply to any tag inside any heading tags): <h3>Payment details <small>(this is your default card)</small></h3> Many Thanks Yes, that markup validates. You can check it yourself on http://validator.w3.org/ Something to be aware of with HTML5 though is a change to the notion of block-level elements: https://developer.mozilla.org/en/HTML/Block-level_elements I don't think there's any restriction on this in the spec. Only Void elements cannot have children.

Adding ID attribute to all HTML elements of a web application?

由 99封情书 提交于 2019-12-04 21:40:29
问题 Currently I am building a web portal using RoR, MySQL, HTML, CSS and jQuery etc., I got a request from my automation test engineer to add ID attributes(if possible NAME attribute also) to all the elements of my application. I am confused to do this perhaps I am not sure whether it is a good practice or not, so can anybody please help me with specific disadvantages/issues with adding ID attributes to all elements of my application. Thanks, Siva 回答1: To do reliable frontend tests, you need to

W3C HTML validation for React JSX files

由 时光总嘲笑我的痴心妄想 提交于 2019-12-04 18:45:15
问题 When working on front-end projects I always like to work with linting tools. They prevent from dumb mistakes to serious smelly code pieces. Linting tools also suggest improvements and optimisations. Validating and linting HTML means using the W3C Validator. When working with vanilla JavaScript projects I use the grunt-html Grunt NPM module. And when working with Angular 1.x I use the grunt-html-angular-validate module, which is the same validator but adapted to Angular requirements (non

Margin collapse and clearance [closed]

由 喜欢而已 提交于 2019-12-04 18:39:37
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 5 years ago . I am reading the W3C specs and I really don't understand that one : If the top and bottom margins of an element with clearance are adjoining, its margins collapse with the adjoining margins of following siblings but that resulting margin does not collapse with the bottom margin of the parent block. Anyone could explain or JSFiddle it for me ? Yes. Take a look at this jsfiddle in

HGROUP element removed from the HTML5 Specification. What alternative technique can be used instead?

由 假装没事ソ 提交于 2019-12-04 18:09:12
问题 As some of you would of heard the hgroup element is being removed from the HTML5 Specification. (For more info, see the W3C HTML Working Group's decision on request to drop hgroup from HTML5 on the W3C's Public Mailing List archives.) Now I'm currently working on the redesign of a site using this tag that creates a way of adding a sub heading. My current thoughts are to just add another hX tag under the main header, but I'm not sure if this would be semantic enough to do so. <h1>Darren Reay<

restriction of elements based on another attribute using XSD 1.1

由 匆匆过客 提交于 2019-12-04 16:15:27
I am trying to create a schema definition using XSD 1.1 in which the number of other elements is dependent on the attribute of another element. E.g. The number of the BaPath elements BaPath depends on the value of the attribute "service" of the "Conn" element. The xsd I wrote is <?xml version="1.0" encoding="UTF-8"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <xsd:element name="Mapping"> <xsd:complexType> <xsd:sequence> <xsd:element ref="Link" minOccurs="0" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="Env"> <xsd:complexType> <xsd

W3C document states

由 …衆ロ難τιáo~ 提交于 2019-12-04 15:59:07
Within the standards that W3C create, do they have a set of states they go through before they are a standard and what are those states ? For example HTML 5.1 currently is in Working Draft . The process is typically linked in the section "Status of This Document". For HTML 5.1, it says : This document is governed by the 1 August 2014 W3C Process Document . This links to the World Wide Web Consortium Process Document from 2014-08-01 (the latest version is always accessible from http://www.w3.org/Consortium/Process/ ). For technical reports that should become Recommendations, this is the process
订阅 w3c