HTML WG - Daily Digest

2007-04-16

Yesterday's interesting posts

1. About indent element

Use indent element to make a block emphasized, noted? What is people make an indent block for?

Or if you need an emphasizing element that can take block content, propose be allowed or suggest a new <blockem> element.</blockem>

2. Versioning and Switches

This is a major issue of these days.

If "always standards mode"(with <!DOCTYPE html>) is set as default of IE.next:

Existing pages might will be broken (because IE.next will process the pages as HTML.new )
There is no needs for authers to write a opt-in switche in their new documents

If opt-in switches are required to handle pages as HTML.new in IE.next:

Existing pages will not be broken.
Authers have to write a Ugly switch in thier documents to process their documents as HTML.new

We all agree that an opt-in is *required* for improved rendering and standards support in IE.next. This is something really "ugly", and we all don't like it, but we have to accept it.

2007-04-13

Digest 2007-04-15

Issue about DOCTYPE used to switch browser rendering modes(e.g. Ki kiosk mode) and compatibility

The "Versioning" thread is making progress.

IE7:
<!DOCTYPE html> : Standard mode
<!DOCTYPE html5>: Standard mode
-Nope, because we look for <!DOCTYPE. We just don't compare to the root element name. A good point, though.

Firefox, Safari:
<!DOCTYPE html> : Standard mode
<!DOCTYPE html5>: Kiosk mode
-What they don't recognise is <!DOCTYPE html5>.

So "<!DOCTYPE html5>" is forward compatible for IE7, but not for Firefox and Safari. But using "<!DOCTYPE html>" to get backward compatibility(to switch to the standard mode) in the new-HTML documents takes a difficulty in handling new-HTML-specific elements.

About formal definition of HTML5

All what we have is only English prose.

Proposing <indent> vs. <blockquote>
The thread is making progress.
It seems that the point of this thread is support for HTML authoers.

Proposing <indent> vs. <blockquote>

Digest 2007-04-13

Topics of yesterday are:

1. What is the spec for mainly? and possibility to split into several specs.

2. Implementation issue and DOCTYPE.

Some discussions about DOCTYPE and backward compatibility.

The current HTML5 spec has severe breakages from IE's implementation already.

And I found a topic about HTML WG at the Slashdot

Apple, Opera, and Mozilla Push For HTML5

2007-04-12

Digest 2007-04-11

The main topic yesterday was about "Proposal to adapt HTML5". HTML5 is a specification from WHAT WG as you know.

From the ML:

explanations of the reasoning behind adding/removing/changing a particular element or attribute?

I'm interested in having someone present HTML5, or the differences between HTML4 and HTML5, in a teleconference.

The point is to have a guide to the Web Apps 1.0 specifications, as the 696 pages are a bit much to internalize all at once

And a new thread by Daniel Glazman is also important:

Here's what I have in mind : have two different status for people in this WG, "participant" and "observer".

Btw, cannot I write DL-DT list on this blog...?

2007-04-11

Getting started

I read a post "wg members status" from Daniel Glazman and realized that I had never posted any mail to the mailing list yet. Hmm I'm getting to be a observer.

So I start this blog to contribute the WG and to help other observers to understand what's happening in the WG (in fact, it's still hard just to follow the discussions, I think).