Recherche avancée

Sur d’autres sites (4716)

• Why I became a HTML5 co-editor

  1er janvier 2014, par silvia

  A few weeks ago, I had the honor to be appointed as part of the editorial team of the W3C HTML5 specification.

  Since Ian Hickson had recently decided to focus solely on editing the WHATWG HTML living standard specification, the W3C started looking for other editors to take the existing HTML5 specification to REC level. REC level is what other standards organizations call a “ratified standard”.

  But what does REC level really mean for HTML ?

  In my probably somewhat subjective view, recommendation level means that a snapshot is taken of the continuously evolving HTML spec, which has a comprehensive feature set, that is implemented in a cross-browser interoperable way, has a complete test set for the features, and has received wide review. The latter implies that other groups in the W3C have had a chance to look at the specification and make sure it satisfies their basic requirements, which include e.g. applicability to all users (accessibility, internationalization), platforms, and devices (mobile, TV).

  Basically it means that we stop for a “moment”, take a deep breath, polish the feature set that we’ve been working on this far, and make sure we all agree on it, before we get back to changing the world with cool new stuff. In a software project we would call it a release branch with feature freeze.

  Now, as productive as that may sound for software – it’s not actually that exciting for a specification. Firstly, the most exciting things happen when writing new features. Secondly, development of browsers doesn’t just magically stop to get the release (REC) happening. And lastly, if we’ve done our specification work well, there should be only little work to do. Basically, it’s the unthankful work of tidying up that we’re looking at here.

  So, why am I doing it ? I am not doing this for money – I’m currently part-time contracting to Google’s accessibility team working on video accessibility and this editor work is not covered by my contract. It wasn’t possible to reconcile polishing work on a specification with the goals of my contract, which include pushing new accessibility features forward. Therefore, when invited, I decided to offer my spare time to the W3C.

  I’m giving this time under the condition that I’d only be looking at accessibility and video related sections. This is where my interest and expertise lie, and where I’m passionate to get things right. I want to make sure that we create accessibility features that will be implemented and that we polish existing video features. I want to make sure we don’t digress from implementations which continue to get updated and may follow the WHATWG spec or HTML.next or other needs.

  I am not yet completely sure what the editorship will entail. Will we look at tests, too ? Will we get involved in HTML.next ? This far we’ve been preparing for our work by setting up adequate version control repositories, building a spec creation process, discussing how to bridge to the WHATWG commits, and analysing the long list of bugs to see how to cope with them. There’s plenty of actual text editing work ahead and the team is shaping up well ! I look forward to the new experiences.

• Core : Update elementValue method to deal with type="number" fields

  29 avril 2014, par jamierytlewski

  Core : Update elementValue method to deal with type="number" fields
  The HTML5 draft defines, for type="number" inputs : "The value
  
  sanitization algorithm is as follows : If the value of the element is not
  
  a valid floating-point number, then set it to the empty string instead."
  
  If the constraint validation considers the input invalid, return false
  
  as the value, instead of the empty string, for the number and digit
  
  methods to output their messages.
  This would break in browsers that support type="number", but not the
  
  constraint validation API. I don’t know of any existing browser where
  
  that applies.
  Fixes #858
  
  Fixes #922
  
  Closes #1093
  

• Normalise offsetX and offsetY on the event

  19 février 2014, par chriscbrock

  Normalise offsetX and offsetY on the event
  According to the W3C Working Draft, offsetX and offsetY should be
  
  relative to the padding edge of the target element. The only browser
  
  using this convention is IE. Webkit uses the border edge, Opera uses the
  
  content edge, and FireFox does not support the properties.
  Normalizing to the border edge is easiest to do.