XForms Status Update

| | Comments (0)

Checked in

  • We were not refreshing the controls if we replaced the instance on <submission> (bug 292616)

  • <setindex> was not working properly for for nested repeats (bug 289547). This removes any id attributes from the cloned repeat content, which ensures that the id is unique (or at least not less unique than before we started messing with the DOM :) )

  • Set trust for XForms events (bug 292319)

  • Emit error messages when something fails the “same origin” security check (bug 292724)

  • Fixed two issues with MIP properties (readonly, relevant, etc.) with <repeat> content. First, MIPs were not applied at all to the content (bug 292089). Second, we not apply the MIP for the context node for “repeat rows” (bug 292725). This means the entire repeat row content matches f.x. :readonly (or rather [readonly] for now).

In Progress

  • We are waiting for superreview on the new XTF+XBL design (bug 291026), so we can get the widgets working (bug 289434)

  • Pseudo class handling still crawling (bug 271720)

  • Waiting for second round of superreview on the attribute handling (bug 235512)

  • Support for evaluating XPath expressions with specific context position and size is waiting for superreview (bug 292841). This will make it possibly for us to support f.x. position() properly (bug 265460).

  • Fix timing problems for bindings when f.x. the model is not the first defined element (bug 283737)

XForms on Minimo

Aaron has gotten XForms working on minimo:

XForms on Minimo screenshot

That’s pretty cool I think.

Current Status

I’ve also updated the status page on moz.org, so it should reflect the current code status.

Leave a comment

About this Entry

This page contains a single entry by beaufour published on May 5, 2005 9:36 AM.

XForms Status Update was the previous entry in this blog.

XForms Status Update is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.

Powered by Movable Type 4.1