Ticket #1329 (new enhancement)
Support for robust record in FF2, play in IE7
| Reported by: | Joonas Lehtinen | Owned by: | Jani Laakso |
|---|---|---|---|
| Priority: | undefined | Milestone: | Testing Tools Backlog |
| Component: | Testing Tools | Version: | |
| Keywords: | Cc: | ville.ingman@…, jani.laakso@…, matti.tahvonen@…, sami.ekblad@… | |
| Known Issue description: | |||
| Hours estimate: | 60 | Deadline (dd.mm.yyyy): | |
| Known Issue version (since): | Known Issue title: | ||
| Hours done: | Depends to: | ||
| Affects documentation: | no | ||
| Known Issue workaround: | |||
| Affects release notes: | yes | Contract: | |
Description (last modified by Joonas Lehtinen) (diff)
Sales indicate that this is a really important killer feature.
One possible implementation model would be to:
- Allow (client-side) widgets to optionally implement String encodeRecordedEvent(DOM-node, event) and void playEncodedEvent(String encodedEvent)
- For any widget implementing above API, use it to create "event encoding" instead of the current DOM-method. Thus the testing tools would really understand what the event means - it is not just a random DOM-event.
- When playing, use above API to play back events (instead of just simulating DOM-events)
- Allow widgets to support path-encoding.
This way layouts (for example) could say that /grid(3,2)/ instead of /3/4/1/0/3/ (just DOM child list iterations).
Change History
Note: See
TracTickets for help on using
tickets.
