haikuwebkit/LayoutTests/accessibility/auto-fill-crash.html

35 lines
1.2 KiB
HTML
Raw Permalink Normal View History

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<html>
<head>
<meta charset="utf-8">
<script src="../resources/js-test-pre.js"></script>
</head>
<body id="body">
<input type="text" value="hello" id="textfield">
<p id="description"></p>
<div id="console"></div>
<script>
description("This tests that when an auto fill element is removed we won't crash accessing an old value.");
if (window.accessibilityController) {
var axTextField = accessibilityController.accessibleElementById("textfield");
[GTK] accessibility/gtk/entry-and-password.html is failing since r194847 https://bugs.webkit.org/show_bug.cgi?id=153062 Reviewed by Carlos Garcia Campos. Source/WebCore: The changes in r194847 include using WebCore's rendering for the CapsLock indicator. As a side effect, password inputs gained a TextControlInnerTextElement child from the Shadow DOM. If we include that child in the accessibility tree, the child will emit focus and text notifications that suggest the user is no longer in the control. This can be especially problematic for screen reader users with key echo enabled when typing in a password input. To fix this, prune TextControlInnerTextElement children from the accessibility tree for ATK. No new tests as existing coverage caught this regression. Also modified the auto-fill-crash.html test whose expectations include the children count for a text input. * accessibility/atk/AccessibilityObjectAtk.cpp: (WebCore::AccessibilityObject::accessibilityPlatformIncludesObject): LayoutTests: The auto-fill-crash.html test has expectations which include the children count for the text input. These expectations were incorrect for ATK where accessible text inputs lack accessible text children. * accessibility/auto-fill-crash.html: Modified to take platform into account. * platform/gtk/TestExpectations: Unskipped entry-and-password.html. * platform/gtk/accessibility/auto-fill-crash-expected.txt: Added. Canonical link: https://commits.webkit.org/174850@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@199715 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2016-04-19 09:50:26 +00:00
var childrenCountExpected = accessibilityController.platformName == "atk" ? "2" : "3";
window.internals.setShowAutoFillButton(document.getElementById("textfield"), "Contacts");
[GTK] accessibility/gtk/entry-and-password.html is failing since r194847 https://bugs.webkit.org/show_bug.cgi?id=153062 Reviewed by Carlos Garcia Campos. Source/WebCore: The changes in r194847 include using WebCore's rendering for the CapsLock indicator. As a side effect, password inputs gained a TextControlInnerTextElement child from the Shadow DOM. If we include that child in the accessibility tree, the child will emit focus and text notifications that suggest the user is no longer in the control. This can be especially problematic for screen reader users with key echo enabled when typing in a password input. To fix this, prune TextControlInnerTextElement children from the accessibility tree for ATK. No new tests as existing coverage caught this regression. Also modified the auto-fill-crash.html test whose expectations include the children count for a text input. * accessibility/atk/AccessibilityObjectAtk.cpp: (WebCore::AccessibilityObject::accessibilityPlatformIncludesObject): LayoutTests: The auto-fill-crash.html test has expectations which include the children count for the text input. These expectations were incorrect for ATK where accessible text inputs lack accessible text children. * accessibility/auto-fill-crash.html: Modified to take platform into account. * platform/gtk/TestExpectations: Unskipped entry-and-password.html. * platform/gtk/accessibility/auto-fill-crash-expected.txt: Added. Canonical link: https://commits.webkit.org/174850@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@199715 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2016-04-19 09:50:26 +00:00
shouldBe("accessibilityController.accessibleElementById('textfield').childrenCount", childrenCountExpected);
// Don't crash!
[GTK] accessibility/gtk/entry-and-password.html is failing since r194847 https://bugs.webkit.org/show_bug.cgi?id=153062 Reviewed by Carlos Garcia Campos. Source/WebCore: The changes in r194847 include using WebCore's rendering for the CapsLock indicator. As a side effect, password inputs gained a TextControlInnerTextElement child from the Shadow DOM. If we include that child in the accessibility tree, the child will emit focus and text notifications that suggest the user is no longer in the control. This can be especially problematic for screen reader users with key echo enabled when typing in a password input. To fix this, prune TextControlInnerTextElement children from the accessibility tree for ATK. No new tests as existing coverage caught this regression. Also modified the auto-fill-crash.html test whose expectations include the children count for a text input. * accessibility/atk/AccessibilityObjectAtk.cpp: (WebCore::AccessibilityObject::accessibilityPlatformIncludesObject): LayoutTests: The auto-fill-crash.html test has expectations which include the children count for the text input. These expectations were incorrect for ATK where accessible text inputs lack accessible text children. * accessibility/auto-fill-crash.html: Modified to take platform into account. * platform/gtk/TestExpectations: Unskipped entry-and-password.html. * platform/gtk/accessibility/auto-fill-crash-expected.txt: Added. Canonical link: https://commits.webkit.org/174850@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@199715 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2016-04-19 09:50:26 +00:00
childrenCountExpected = accessibilityController.platformName == "atk" ? "0" : "1";
window.internals.setShowAutoFillButton(document.getElementById("textfield"), "None");
[GTK] accessibility/gtk/entry-and-password.html is failing since r194847 https://bugs.webkit.org/show_bug.cgi?id=153062 Reviewed by Carlos Garcia Campos. Source/WebCore: The changes in r194847 include using WebCore's rendering for the CapsLock indicator. As a side effect, password inputs gained a TextControlInnerTextElement child from the Shadow DOM. If we include that child in the accessibility tree, the child will emit focus and text notifications that suggest the user is no longer in the control. This can be especially problematic for screen reader users with key echo enabled when typing in a password input. To fix this, prune TextControlInnerTextElement children from the accessibility tree for ATK. No new tests as existing coverage caught this regression. Also modified the auto-fill-crash.html test whose expectations include the children count for a text input. * accessibility/atk/AccessibilityObjectAtk.cpp: (WebCore::AccessibilityObject::accessibilityPlatformIncludesObject): LayoutTests: The auto-fill-crash.html test has expectations which include the children count for the text input. These expectations were incorrect for ATK where accessible text inputs lack accessible text children. * accessibility/auto-fill-crash.html: Modified to take platform into account. * platform/gtk/TestExpectations: Unskipped entry-and-password.html. * platform/gtk/accessibility/auto-fill-crash-expected.txt: Added. Canonical link: https://commits.webkit.org/174850@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@199715 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2016-04-19 09:50:26 +00:00
shouldBe("accessibilityController.accessibleElementById('textfield').childrenCount", childrenCountExpected);
}
</script>
<script src="../resources/js-test-post.js"></script>
</body>
</html>