To clear up one point, eValid tracks the frame path by the NAMES
of the paths...not an ID tag in each frame.
(e.g) ...frame id B -> frame id A you really mane ...frame-name
B =-> frame-name A.
We created a simple example that has the names in a screwy
order and eValid's PageMap finds the names perfectly correctly,
even when several frame have identical names...
www.soft.com/Test/Frames/NestedFrames/non-normal.htmlTry your eValid PageMap on this page and you'll see that either
with ordinal numbering or naturanl (non-ordinal) eValid does
the right thing.
We now believe that the reason the Firefox page frame sequence
worked is that the frames had changed names (and changed
nesting) between when the recording was made and when the playback
happened...