Closed Bug 1932280 Opened 7 months ago Closed 7 months ago

High frequency Android layout/base/tests/test_interactive_widget.html | the visual viewport height (560) is less than the visual viewport width (800), it hightly suspects the virtual keyboard persists there, thus we can't run this interactive-widget tests

Categories

(Core :: Layout, defect)

Product:
Core
Component:
Layout
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
134 Branch
Tracking Flags:
Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- unaffected
firefox132 --- unaffected
firefox133 --- unaffected
firefox134 --- fixed

People

(Reporter: intermittent-bug-filer, Unassigned)

References

(Regression)

Details

(Keywords: intermittent-failure, intermittent-testcase, regression)

Filed by: sstanca [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=483415209&repo=mozilla-central
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/fI_4N24yQjSiNXM3EZZyZw/runs/0/artifacts/public/logs/live_backing.log

[task 2024-11-20T02:04:04.917Z] 02:04:04     INFO -  TEST-OK | layout/base/tests/test_getClientRects_emptytext.html | took 364ms
[task 2024-11-20T02:04:04.917Z] 02:04:04     INFO -  TEST-START | layout/base/tests/test_interactive_widget.html
[task 2024-11-20T02:04:04.917Z] 02:04:04     INFO -  Buffered messages logged at 02:03:58
[task 2024-11-20T02:04:04.917Z] 02:04:04     INFO -  add_setup | Entering
[task 2024-11-20T02:04:04.917Z] 02:04:04     INFO -  Buffered messages finished
[task 2024-11-20T02:04:04.918Z] 02:04:04  WARNING -  TEST-UNEXPECTED-FAIL | layout/base/tests/test_interactive_widget.html | the visual viewport height (560) is less than the visual viewport width (800), it hightly suspects the virtual keyboard persists there, thus we can't run this interactive-widget tests properly
[task 2024-11-20T02:04:04.918Z] 02:04:04     INFO -      SimpleTest.ok@SimpleTest/SimpleTest.js:426:16
[task 2024-11-20T02:04:04.918Z] 02:04:04     INFO -      @layout/base/tests/test_interactive_widget.html?currentTestURL=layout%2Fbase%2Ftests%2Ftest_interactive_widget.html&closeWhenDone=1&showTestReport=false&expected=pass:79:5
[task 2024-11-20T02:04:04.918Z] 02:04:04     INFO -      async*nextTick/<@SimpleTest/SimpleTest.js:2213:34
[task 2024-11-20T02:04:04.918Z] 02:04:04     INFO -      nextTick@SimpleTest/SimpleTest.js:2257:11
[task 2024-11-20T02:04:04.918Z] 02:04:04     INFO -      setTimeout handler*SimpleTest_setTimeoutShim@SimpleTest/SimpleTest.js:922:41
[task 2024-11-20T02:04:04.918Z] 02:04:04     INFO -      add_task@SimpleTest/SimpleTest.js:2161:17
[task 2024-11-20T02:04:04.918Z] 02:04:04     INFO -      add_setup@SimpleTest/SimpleTest.js:2277:10
[task 2024-11-20T02:04:04.919Z] 02:04:04     INFO -      @layout/base/tests/test_interactive_widget.html?currentTestURL=layout%2Fbase%2Ftests%2Ftest_interactive_widget.html&closeWhenDone=1&showTestReport=false&expected=pass:34:10
[task 2024-11-20T02:04:04.919Z] 02:04:04     INFO -  add_setup | Leaving
[task 2024-11-20T02:04:04.919Z] 02:04:04     INFO -  add_task | Entering
[task 2024-11-20T02:09:07.926Z] 02:09:07  WARNING -  TEST-UNEXPECTED-FAIL | layout/base/tests/test_interactive_widget.html | Test timed out. -
[task 2024-11-20T02:09:07.927Z] 02:09:07     INFO -  TEST-OK | layout/base/tests/test_interactive_widget.html | took 306760ms

Set release status flags based on info from the regressing bug 1929160

:m_kato, since you are the author of the regressor, bug 1929160, could you take a look?

For more information, please visit BugBot documentation.

status-firefox132: --- → unaffected
status-firefox133: --- → unaffected
status-firefox134: --- → affected
status-firefox-esr128: --- → unaffected
Flags: needinfo?(m_kato)

Hi Makoto! Could you please take a look at this? It seems that this has a high rate of failing on Android since your push has landed, as it can be seen here.

Thank you!

status-firefox132: unaffected → ---
status-firefox133: unaffected → ---
status-firefox134: affected → ---
status-firefox-esr128: unaffected → ---
Severity: S4 → --
Priority: P5 → --

There are a couple of tests setting designMode in the same directly, if we don't need to open the software keyboard in the test, we can just put "inputmode=none" there?

See Also: → 1918577

Set release status flags based on info from the regressing bug 1929160

status-firefox132: --- → unaffected
status-firefox133: --- → unaffected
status-firefox134: --- → affected
status-firefox-esr128: --- → unaffected

Hmm, test_interactive_widget.html doesn't use design mode... I think I should request backed out of bug 1929160 to investigate more.

Flags: needinfo?(m_kato)

Backed out bug 1929160

Status: NEW → RESOLVED
Closed: 7 months ago
Resolution: --- → FIXED

(In reply to Makoto Kato [:m_kato] from comment #5)

Hmm, test_interactive_widget.html doesn't use design mode... I think I should request backed out of bug 1929160 to investigate more.

No, the reason of the test failure is that there's at least one test run before test_interactive_widget.html and the test opens the software keyboard and the keyboard keeps opening there, thus test_interactive_widget.html failed.

What we need to do here is that, I believe, setting inputmode=none in tests in comment 3. I believe it will solve the test_interactive_widget.html failure.

status-firefox134: affected → fixed
status-firefox-esr115: --- → unaffected
Target Milestone: --- → 134 Branch
You need to log in before you can comment on or make changes to this bug.