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

53 строки
1.9 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 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">
SimpleTest.waitForExplicitFinish();
SimpleTest.waitForFocus(function nextTest() {
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");
div.parentNode.removeChild(div);
nextTest();
}, function() {
ok(false, "failed to copy the expected content to the clipboard");
SimpleTest.finish();
});
});
</script>
</body>
</html>