mozilla
/
gecko-dev
зеркало из https://github.com/mozilla/gecko-dev.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
gecko-dev/dom/base/test/test_bug116083.html

104 строки
5.6 KiB
HTML
Исходник Обычный вид История

Bug 116083 - Correctly handle the whitespace in all preformatted elements; r=roc Previously this code only handled the special case of a <body> element that had an explicit style attribute, which doesn't really make sense. Now we do the right thing based on the computed white-space style.
2014-12-01 14:38:11 +03:00
<!DOCTYPE HTML>
<html>
<!--
https://bugzilla.mozilla.org/show_bug.cgi?id=116083
-->
<head>
<title>Test for Bug 116083</title>
<script type="application/javascript" src="/tests/SimpleTest/SimpleTest.js"></script>
<script type="application/javascript" src="/tests/SimpleTest/EventUtils.js"></script>
<link rel="stylesheet" type="text/css" href="/tests/SimpleTest/test.css"/>
</head>
<body>
<a target="_blank" href="https://bugzilla.mozilla.org/show_bug.cgi?id=116083">Mozilla Bug 116083</a>
<div id="content">
<div style="white-space: pre">foo bar</div>
<div style="white-space: pre-wrap">foo bar</div>
<div style="white-space: pre-line">foo bar</div>
<div style="white-space: -moz-pre-space">foo bar</div>
Bug 1113238 - Part 1: Make our plaintext and HTML serializers aware of CSS preformatted styles; r=bzbarsky This code is super-hairy, but I think this is the minimum amount of changes that we need. nsPlainTextSerializer::IsInPre() before this patch is completely broken, and I changed it to maintain a stack of bools representing whether the elements that we saw as we were traversing the tree are preformatted or not. nsXHTMLContentSerializer maintains this information using a counter, which is broken in case pre and non-preformatted elements are stacked underneath each other, but I'm not sure why this code is using a counter and I didn't want to change it drastically, so for now I'm just making it look at the element's style first as opposed to its tag name. Follow-up work may include exploring whether nsXHTMLContentSerializer should use a stack similar to nsPlainTextSerializer, and also audit this code for more places where things are hardcoded based on tag names where we should be really looking at the style.
2014-12-19 20:45:50 +03:00
<div data-result="bar baz"><span style="white-space: pre">bar </span>baz</div>
<div data-result="bar baz"><span style="white-space: pre-wrap">bar </span>baz</div>
<div data-result="bar baz"><span style="white-space: pre-line">bar </span>baz</div>
<div data-result="bar baz"><span style="white-space: -moz-pre-space">bar </span>baz</div>
Bug 1119503 - Part 2: Insert a line break between preformatted block boundaries when creating raw output; r=bzbarsky
2015-01-18 01:31:59 +03:00
<div data-result="foo &#10; bar&#10;&#10;!&#10;&#10;&#10;baz" style="white-space: pre"><div>foo </div><div> bar</div><div><br></div><div>!</div><div><br><br></div><div>baz</div></div>
<div data-result="foo &#10; bar&#10;&#10;!&#10;&#10;&#10;baz" style="white-space: pre" contenteditable><div>foo </div><div> bar</div><div><br></div><div>!</div><div><br><br></div><div>baz</div></div>
<div data-result="foo &#10; bar&#10;&#10;!&#10;&#10;&#10;baz" style="white-space: pre-wrap"><div>foo </div><div> bar</div><div><br></div><div>!</div><div><br><br></div><div>baz</div></div>
<div data-result="foo &#10; bar&#10;&#10;!&#10;&#10;&#10;baz" style="white-space: pre-wrap" contenteditable><div>foo </div><div> bar</div><div><br></div><div>!</div><div><br><br></div><div>baz</div></div>
<div data-result="foo &#10; bar&#10;&#10;!&#10;&#10;&#10;baz" style="white-space: pre-line"><div>foo </div><div> bar</div><div><br></div><div>!</div><div><br><br></div><div>baz</div></div>
<div data-result="foo &#10; bar&#10;&#10;!&#10;&#10;&#10;baz" style="white-space: pre-line" contenteditable><div>foo </div><div> bar</div><div><br></div><div>!</div><div><br><br></div><div>baz</div></div>
<div data-result="foo &#10; bar&#10;&#10;!&#10;&#10;&#10;baz" style="white-space: -moz-pre-space"><div>foo </div><div> bar</div><div><br></div><div>!</div><div><br><br></div><div>baz</div></div>
<div data-result="foo &#10; bar&#10;&#10;!&#10;&#10;&#10;baz" style="white-space: -moz-pre-space" contenteditable><div>foo </div><div> bar</div><div><br></div><div>!</div><div><br><br></div><div>baz</div></div>
Bug 1143570 - Part 1: Use an nsBlockInFlowLineIterator to determine whether a BR frame is visible or not; r=roc
2015-05-11 20:36:56 +03:00
<div data-result="foo&#10;bar&#10;baz&#10;qux"><div>foo<br></div><span>bar<br>baz<br>qux</span></div>
<div data-result="foo&#10;bar&#10;baz&#10;qux" contenteditable><div>foo<br></div><span>bar<br>baz<br>qux</span></div>
<div data-result="foo&#10;&#10;"><div>foo</div><span><br></span></div>
<div data-result="foo&#10;&#10;" contenteditable><div>foo</div><span><br></span></div>
<div data-result="foo&#10;&#10;bar"><div>foo</div><span><br></span><div>bar</div></div>
<div data-result="foo&#10;&#10;bar" contenteditable><div>foo</div><span><br></span><div>bar</div></div>
<div data-result="foo&#10;bar&#10;"><div>foo</div><span>bar<br></span></div>
<div data-result="foo&#10;bar" contenteditable><div>foo</div><span>bar<br></span></div>
<div data-result="foo&#10;bar&#10;baz"><div>foo</div><span>bar<br></span><div>baz</div></div>
<div data-result="foo&#10;bar&#10;baz" contenteditable><div>foo</div><span>bar<br></span><div>baz</div></div>
<div data-result="&#10;&#10;foo"><div><br><br><div>foo</div></div></div>
<div data-result="&#10;&#10;foo" contenteditable><div><br><br><div>foo</div></div></div>
<div data-result="foo&#10;bar"><div>foo<br>bar</div></div>
<div data-result="foo&#10;bar" contenteditable><div>foo<br>bar</div></div>
<div data-result="foo&#10;bar&#10;"><div>foo<br>bar<br></div></div>
<div data-result="foo&#10;bar" contenteditable><div>foo<br>bar<br></div></div>
Bug 116083 - Correctly handle the whitespace in all preformatted elements; r=roc Previously this code only handled the special case of a <body> element that had an explicit style attribute, which doesn't really make sense. Now we do the right thing based on the computed white-space style.
2014-12-01 14:38:11 +03:00
<div data-result="&#10;foo bar&#10;">foo bar</div>
</div>
<script type="application/javascript">
Bug 1151873 - Unit test
2015-04-09 16:55:48 +03:00
const Cc = SpecialPowers.Cc;
const Ci = SpecialPowers.Ci;
function hasExpectedFlavors() {
var cb = Cc["@mozilla.org/widget/clipboard;1"].
getService(Ci.nsIClipboard);
Bug 1270277, HasDataMatchingFlavors should only return true for text/unicode, r=snorp
2016-05-11 17:04:19 +03:00
ok(cb.hasDataMatchingFlavors(["text/unicode"], 1, cb.kGlobalClipboard),
"The clipboard has text/unicode");
// Android only supports plain text
Bug 1339461 - script-generated patch to convert foo.indexOf(...) == -1 to foo.includes(), r=Mossop.
2018-02-01 22:45:22 +03:00
if (!navigator.appVersion.includes("Android")) {
Bug 1270277, HasDataMatchingFlavors should only return true for text/unicode, r=snorp
2016-05-11 17:04:19 +03:00
ok(cb.hasDataMatchingFlavors(["text/html"], 1, cb.kGlobalClipboard),
"The clipboard has text/html");
}
Bug 1339461 - script-generated patch to convert foo.indexOf(...) == -1 to foo.includes(), r=Mossop.
2018-02-01 22:45:22 +03:00
if (navigator.appVersion.includes("Win")) {
Bug 1270277, HasDataMatchingFlavors should only return true for text/unicode, r=snorp
2016-05-11 17:04:19 +03:00
ok(cb.hasDataMatchingFlavors(["application/x-moz-nativehtml"], 1, cb.kGlobalClipboard),
"The clipboard has application/x-moz-nativehtml");
}
Bug 1151873 - Unit test
2015-04-09 16:55:48 +03:00
}
Bug 1210265 - Add a pref toggle for copying/pasting only plain text on B2G. r=timdream Add a new preference, clibboard.plainTextOnly. 1. On: we only support kUnicodeMIME in SetData/GetData. 2. Off: we can support different MIME types in SetData/GetData BTW, "copy image" is dependent on non-text/rich text support, so this menu item is also disabled after we turn the pref off.
2015-10-02 01:26:00 +03:00
function nextTest() {
Bug 116083 - Correctly handle the whitespace in all preformatted elements; r=roc Previously this code only handled the special case of a <body> element that had an explicit style attribute, which doesn't really make sense. Now we do the right thing based on the computed white-space style.
2014-12-01 14:38:11 +03:00
var div = document.querySelector("#content>div");
if (!div) {
SimpleTest.finish();
return;
}
getSelection().selectAllChildren(div);
var expected = div.hasAttribute("data-result") ?
div.getAttribute("data-result") :
div.textContent;
SimpleTest.waitForClipboard(expected, function() {
synthesizeKey("C", {accelKey: true});
}, function() {
ok(true, div.getAttribute("style") + " passed");
Bug 1270277, HasDataMatchingFlavors should only return true for text/unicode, r=snorp
2016-05-11 17:04:19 +03:00
hasExpectedFlavors();
Bug 1334831 - script-generated patch to use .remove() instead of .parentNode.removeChild, r=jaws.
2017-01-30 10:10:22 +03:00
div.remove();
Bug 116083 - Correctly handle the whitespace in all preformatted elements; r=roc Previously this code only handled the special case of a <body> element that had an explicit style attribute, which doesn't really make sense. Now we do the right thing based on the computed white-space style.
2014-12-01 14:38:11 +03:00
nextTest();
}, function() {
ok(false, "failed to copy the expected content to the clipboard");
SimpleTest.finish();
});
Bug 1210265 - Add a pref toggle for copying/pasting only plain text on B2G. r=timdream Add a new preference, clibboard.plainTextOnly. 1. On: we only support kUnicodeMIME in SetData/GetData. 2. Off: we can support different MIME types in SetData/GetData BTW, "copy image" is dependent on non-text/rich text support, so this menu item is also disabled after we turn the pref off.
2015-10-02 01:26:00 +03:00
}
SimpleTest.waitForExplicitFinish();
SimpleTest.waitForFocus(function() {
SpecialPowers.pushPrefEnv({"set": [["clipboard.plainTextOnly", false]]}, nextTest);
Bug 116083 - Correctly handle the whitespace in all preformatted elements; r=roc Previously this code only handled the special case of a <body> element that had an explicit style attribute, which doesn't really make sense. Now we do the right thing based on the computed white-space style.
2014-12-01 14:38:11 +03:00
});
</script>
</body>
</html>