bugs with ".pc-focus" styling and "navindex" attribute.

david_dupont73's picture
Project:formsPlayer
Version:1.5.4.1030
Component:Code
Category:bug
Priority:critical
Assigned:Paul Butcher
Status:new
Attachment:nav_pb.zip (81.68 KB)
Description

Hi, i use the ".pc-focus" style to display in a specific color the current field of my formular and "navindex" attribut to navigate accros the field of my formular.
But It's appear several dysfunction:
- On the xf:input control, the style ".pc-focus" stay apply after leaving it. (It's work with version prior to 1.5.4.1026) (cf.Screenshot pb_on_pc-focus.jpg )
- When the current field is the last, when i press "TAB" key, focus disappear. In XFORM 1.1 Specification, navindex could be cycle.
- As you can see on my second screenshot "pb_on_navindex.jpg", when i use TAB key from control indexed with "navIndex=1" to "navIndex=2", the "pc-focus" style is not setting for "navIndex=2", but if i press "TAB" key twice from "navIndex=1", "pc-focus" styling are setting for the "navIndex=3" control.
- When I was in the xf:date control, i must press "TAB" key twice to arrive at the next "navIndex" control.

Updates

#1 submitted by Paul Butcher on Wed, 2007-10-03 18:13
Assigned to:» Paul Butcher

I am investigating this.

#2 submitted by Paul Butcher on Tue, 2007-10-09 10:51
Title:bugs with ".pc-focus" styling and "navindex" attribut .» bugs with ".pc-focus" styling and "navindex" attribute.
Attachment:1063.htm.txt (3.96 KB)

Firstly, I would advise that issue tracking systems offer a better user experience when issues in the system exist in a one-to-one relationship with conceptual issues. That way, you would be able to see at-a-glance, which issues have been resolved, by looking at their status, rather than having to read through all of this prose in order to discover the status of individual issues.

A fix for the first issue has now been applied,

Regarding the second issue mentioned here, XForms 1.1 states that "The navigation sequence past the last form control (or before the first) is undefined. XForms Processors may cycle back to the first/last control, remove focus from the form, or other possibilities.", in formsPlayer under IE, navigating past the last field or before the first sets focus to the surrounding application, once the last focus-receiving element of the surrounding application is tabbed away from, the first node in the HTML document will receive focus.

I am continuing to investigate the third issue.

The Fourth Issue is demonstrated in the attached file to be fixed in 1.5.4.1034