This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21813 - First code example below 3.2.1 Semantics
Summary: First code example below 3.2.1 Semantics
Status: RESOLVED MOVED
Alias: None
Product: HTML.next
Classification: Unclassified
Component: default (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL: http://www.plam.cantech.bg
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-24 14:59 UTC by Devarshi Pant
Modified: 2016-04-28 16:58 UTC (History)
4 users (show)

See Also:


Attachments

Description Devarshi Pant 2013-04-24 14:59:33 UTC
3.2.1 Semantics -> Code Example: 

**
A] Consider http://www.w3.org/html/wg/drafts/html/master/dom.html#semantics-0 and quoting from the spec, "As a simple example, consider a Web page written by an author who only considered desktop computer Web browsers. Because HTML conveys meaning, rather than presentation, the same page can also be used by a small browser on a mobile phone, without any change to the page. Instead of headings being in large letters as on the desktop, for example, the browser on the mobile phone might use the same size text for the whole the page, but with the headings in bold."

It is not clear what the first sentence in the above paragraph is trying to convey, especially when this is about semantics. In the third sentence, headings are introduced to make a point without any reference made whether these were structural to begin with. Also note the grammatical error in "for the whole the page."
**

**
B] Consider the following and quoting from the spec, "But it goes further than just differences in screen size: the same page could equally be used by a blind user using a browser based around speech synthesis, which instead of displaying the page on a screen, reads the page to the user, e.g. using headphones. Instead of large text for the headings, the speech browser might use a different volume or a slower voice."

The reference to 'same page' is confusing. Which page is the 'same page'? 
**

I think that the parts (discussed above) could be rephrased to make them easier to follow. Note that paragraphs 3 and 4 in the spec (below Code example #1) are clear and succinct.

-Devarshi
Comment 1 LĂ©onie Watson 2016-04-28 16:58:25 UTC
Moved to HTML on Github
https://github.com/w3c/html/issues/313