Intermittent toolkit/content/tests/browser/browser_datetime_datepicker.js | datepicker x position: 204 should be equal(-ish) to 214 -
Categories
(Toolkit :: General, defect, P5)
Tracking
()
Tracking | Status | |
---|---|---|
firefox84 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: sefeng)
References
Details
(Keywords: intermittent-failure, Whiteboard: [retriggered][stockwell needswork:owner])
Attachments
(1 file)
Filed by: nbeleuzu [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=318759741&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/QCjERgKtTPqyLQnmZhxZdQ/runs/0/artifacts/public/logs/live_backing.log
[task 2020-10-15T19:01:58.362Z] 19:01:58 INFO - TEST-PASS | toolkit/content/tests/browser/browser_datetime_datepicker.js | "2016-11-27" == "2016-11-27" -
[task 2020-10-15T19:01:58.362Z] 19:01:58 INFO - Leaving test bound test_datepicker_clicked
[task 2020-10-15T19:01:58.363Z] 19:01:58 INFO - Entering test bound test_datepicker_transformed_position
[task 2020-10-15T19:01:58.363Z] 19:01:58 INFO - Buffered messages logged at 19:01:57
[task 2020-10-15T19:01:58.383Z] 19:01:58 INFO - Console message: [JavaScript Error: "The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol." {file: "data:text/html,<iframe id='iframe' src='http://example.net/document-builder.sjs?html=%3Cinput%20id=%22date%22%20type=%22date%22%20value=%222016-12-15%22%20style=%22transform:%20translateX(7px)%20translateY(13px);%20border-top:%202px;%20border-left:%205px;%20margin:%2030px;%22%3E'>" line: 0}]
[task 2020-10-15T19:01:58.383Z] 19:01:58 INFO - Buffered messages finished
[task 2020-10-15T19:01:58.383Z] 19:01:58 INFO - TEST-UNEXPECTED-FAIL | toolkit/content/tests/browser/browser_datetime_datepicker.js | datepicker x position: 204 should be equal(-ish) to 214 -
[task 2020-10-15T19:01:58.384Z] 19:01:58 INFO - Stack trace:
[task 2020-10-15T19:01:58.384Z] 19:01:58 INFO - chrome://mochikit/content/browser-test.js:test_ok:1304
[task 2020-10-15T19:01:58.384Z] 19:01:58 INFO - chrome://mochitests/content/browser/toolkit/content/tests/browser/browser_datetime_datepicker.js:is_close:107
[task 2020-10-15T19:01:58.385Z] 19:01:58 INFO - chrome://mochitests/content/browser/toolkit/content/tests/browser/browser_datetime_datepicker.js:verifyPickerPosition:112
[task 2020-10-15T19:01:58.385Z] 19:01:58 INFO - Not taking screenshot here: see the one that was previously logged
[task 2020-10-15T19:01:58.385Z] 19:01:58 INFO - TEST-UNEXPECTED-FAIL | toolkit/content/tests/browser/browser_datetime_datepicker.js | datepicker y position: 242 should be equal(-ish) to 252 -
[task 2020-10-15T19:01:58.385Z] 19:01:58 INFO - Stack trace:
[task 2020-10-15T19:01:58.385Z] 19:01:58 INFO - chrome://mochikit/content/browser-test.js:test_ok:1304
[task 2020-10-15T19:01:58.385Z] 19:01:58 INFO - chrome://mochitests/content/browser/toolkit/content/tests/browser/browser_datetime_datepicker.js:is_close:107
[task 2020-10-15T19:01:58.385Z] 19:01:58 INFO - chrome://mochitests/content/browser/toolkit/content/tests/browser/browser_datetime_datepicker.js:verifyPickerPosition:113
[task 2020-10-15T19:01:58.386Z] 19:01:58 INFO - GECKO(5635) | [Parent 5635, Main Thread] WARNING: 'NS_FAILED(targetPrincipal->GetAsciiOrigin(targetOrigin))', file /builds/worker/checkouts/gecko/toolkit/components/antitracking/AntiTrackingUtils.cpp:347
[task 2020-10-15T19:01:58.386Z] 19:01:58 INFO - Leaving test bound test_datepicker_transformed_position
[task 2020-10-15T19:01:58.386Z] 19:01:58 INFO - Entering test bound test_datepicker_reopen_state
Comment 1•4 years ago
|
||
Emilio, could these Linux debug failures be a regression from bug 1669742? Bug 1669573 doesn't aim for frontend changed and the content of the date picker looks correct. Bug 1669239 looks unrelated to position.
Comment 2•4 years ago
|
||
That's only a change to CSS serialization, and the relevant media queries are not used in any of the relevant widgets and such, so no...
Bug 1669239 can change scheduling of various things (animation frame callbacks etc), so it'd be my best guess of those three.
Comment 3•4 years ago
|
||
Please check if this is a regression from bug 1669239.
Assignee | ||
Comment 4•4 years ago
|
||
I am working on a patch in bug 1671592 that hopefully can fix it.
Comment hidden (Intermittent Failures Robot) |
Updated•4 years ago
|
Comment 6•4 years ago
|
||
Hi Sean, this is still occurring even after bug 1671592 landed, can you please take a look?
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Comment 8•4 years ago
|
||
Yeah, looking.
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Comment 10•4 years ago
|
||
The position of the date picker relies on the <input> element's
position. In certain tests, we add some CSS properties to the <input>
element to verify date picker's position. However, it's possible
that the CSS properties are not applied. This patch adds two RAFs
to grant an opportunity for CSS styling to complete.
Updated•4 years ago
|
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Updated•4 years ago
|
Comment hidden (Intermittent Failures Robot) |
Comment 14•4 years ago
|
||
Pushed by sefeng@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/84748da9c6a2 Ensure datepicker <iframe> is correctly positioned r=emilio
Comment 15•4 years ago
|
||
bugherder |
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Updated•4 years ago
|
Description
•