Add jQuery support to elementslib to access content elements

RESOLVED WONTFIX

Status

P2
normal
RESOLVED WONTFIX
9 years ago
2 years ago

People

(Reporter: whimboo, Unassigned)

Tracking

Details

(Whiteboard: [qae-p1][mozmill-1.4.2-], URL)

(Reporter)

Description

9 years ago
On some content documents with a lot of dynamic content we have problems to get a correct element string for a node. As Mikeal proposed we could introduce jQuery to be able to get the element.

For now you can see such a behavior with the test posted as URI to this bug. It will work for branded versions but will fail for non-branded builds. Just execute it in Shiretoko.
(Reporter)

Comment 1

9 years ago
In the last days we have discovered a lot of really strange queries when accessing e.g. elements in the autocomplete popup of the location bar. It would really help us when we have a simply way to fetch elements.

Talked with Mikeal about that a couple of times. Setting as P1 for next quarter.
Whiteboard: [qae-p1]

Updated

9 years ago
Priority: -- → P2

Updated

9 years ago
Whiteboard: [qae-p1] → [qae-p1][mozmill-1.4.2-]
(Reporter)

Comment 2

4 years ago
Mozmill will reach its end of life soon. We are currently working on getting all the tests for Firefox ported to Marionette. For status updates please see bug 1080766.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
(Assignee)

Updated

2 years ago
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.