Mac only failure with xpath on Lightning preference pane in thunderbird

RESOLVED WORKSFORME

Status

Testing Graveyard
Mozmill
RESOLVED WORKSFORME
9 years ago
2 years ago

People

(Reporter: cmtalbert, Assigned: cmtalbert)

Tracking

Trunk
x86
Mac OS X

Details

(Whiteboard: [p1-qae][mozmill-1.4.2+])

Attachments

(1 attachment, 1 obsolete attachment)

979 bytes, application/x-javascript
Details
(Assignee)

Description

9 years ago
Created attachment 419042 [details]
The test case to demonstrate the problem

1. Install mozmill into thunderbird with lightning
2. Copy the attached module into the modules directory
3. Copy the test into a test directory 
4. Run the test in mozmill

= Expected =
The xpath would work to select an item in the drop down. - It works on windows and linux

= Actual =
On mac, the xpath expression doesn't work and causes a failure in mozmill.
The dom is not different between the different OS's, so it's really not clear what is going on here.
Clint, do you have the corresponding line of code in Lighting for us?
(Assignee)

Comment 2

9 years ago
(In reply to comment #1)
> Clint, do you have the corresponding line of code in Lighting for us?

http://mxr.mozilla.org/comm-central/source/calendar/base/content/preferences/timezones.xul#64
Just wondering why you do not use a Lookup expression. Accessing elements via their xpath is used rarely at least for our tests in Firefox. Could you check if a Lookup exression will work?
(Assignee)

Updated

8 years ago
Whiteboard: [p1-qae] → [p1-qae][mozmill-1.4.2+]
(Assignee)

Updated

8 years ago
Assignee: nobody → ctalbert
(Assignee)

Comment 4

8 years ago
Created attachment 461563 [details]
Simpler test for the issue

This is a simpler test for the xpath issue.  It's been updated to work with the current version of the prefsAPI, could have been an issue with the old prefsAPI or mozmill so it's hard to know what change caused this to start working, but it works now.
Attachment #419042 - Attachment is obsolete: true
(Assignee)

Comment 5

8 years ago
Marking WFM, and in answer to comment 3, yes a lookup expression would work, but the issue here is that the inspector was giving out an xpath expression, and since the inspector does validation, it should not ever give out an expression that doesn't work, which it was doing in this case.

But as noted in comment 4, looks like we fixed this somewhere along the way.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → WORKSFORME
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.