diff options
author | initial.commit <initial.commit@0039d316-1c4b-4281-b951-d872f2087c98> | 2008-07-26 23:55:29 +0000 |
---|---|---|
committer | initial.commit <initial.commit@0039d316-1c4b-4281-b951-d872f2087c98> | 2008-07-26 23:55:29 +0000 |
commit | 09911bf300f1a419907a9412154760efd0b7abc3 (patch) | |
tree | f131325fb4e2ad12c6d3504ab75b16dd92facfed /chrome/test/data/columns.html | |
parent | 586acc5fe142f498261f52c66862fa417c3d52d2 (diff) | |
download | chromium_src-09911bf300f1a419907a9412154760efd0b7abc3.zip chromium_src-09911bf300f1a419907a9412154760efd0b7abc3.tar.gz chromium_src-09911bf300f1a419907a9412154760efd0b7abc3.tar.bz2 |
Add chrome to the repository.
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/test/data/columns.html')
-rw-r--r-- | chrome/test/data/columns.html | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/chrome/test/data/columns.html b/chrome/test/data/columns.html new file mode 100644 index 0000000..84b688d --- /dev/null +++ b/chrome/test/data/columns.html @@ -0,0 +1,23 @@ +<html><head><title>Column test</title></head><body> +<h1>Column test</h1> + +<p>This tests that we do multi-column layout and don't crash. The issue is +that WebKit creates a NULL platform graphics context pointer, and expects +GraphicsContext to work with it, disabling paint.</p> + +<div style="border: 2px solid rgb(34, 136, 17); -webkit-column-count: 2; +-moz-column-count: 2; -webkit-column-rule: 2px solid rgb(34, 136, 17); +-moz-column-rule: 4px solid rgb(34, 136, 17)">WebKit now has some very basic +support for multiple columns from CSS3. In fact, if you’re reading this +blog entry, you will see that it has been broken up into two columns in the +latest WebKit nightly and in Firefox.<br /> + +<div style="margin: 1em 0">The properties supported at this time are columns, +column-gap, column-count and column-width. Column rules are not yet supported +and neither are column breaks.</div> At this time any stacking context children +like relative positioned content or content that uses opacity will position +impoperly (as though the column didn’t exist. If you decide to use this +feature, watch out for that.<br /> <div style="margin-top:1em"><b>Update</b>: +Column rules are now supported. This blog entry now has one!</div> + +</body></html> |