adobe-webplatform / css-regions-polyfill Goto Github PK

The algorithm should support DOM elements that have the height set as a CSS value rather than calculated based on children content. Right now the algorithm looks only at text nodes and IMG/FIG as a content that has to be fit.

I know this polyfill is a very good code but I was wondering if it's posible to get the last line of a broken (and justified) paragraph justified. Seem the polyfill inserts a [/p] and [p] to break paragraphs, Do will be posible to add an special class to get this kind of paragraphs (justified [p]) with the last (broken) line justified?
Note: [ is < and ] is >

if the flow-from element contains an ID attribute it is copied into the flow-into containers, producing invalid and unexpected results (due to duplicate ID's). I'm not sure if there is a sensible solution for this aside from not giving the content container an ID.

I think the polyfill source has evolved enough to be pulled out of the /playground/src/ folder.
I propose moving it to the root of the project. If that's ok, I can handle the change and update the paths.

document.querySelector("style") throws an error on IE 9. querySelector() should be supported and yet there is an error. Could be related to missing DOCTYPE declaration:

http://msdn.microsoft.com/en-us/library/ie/cc288169(v=vs.85).aspx

Might help with the performance for something like Human Legacy Project example.

No QUnit submodule folder is tracked in the git repository.

git clone git://github.com/jquery/qunit.git test/qunit checked out the latest version, but even after running grunt in that directory, the paths were incorrect.

This prevents me from running the test suite.

A page to link to from html.adobe.com

A clean demo exemplifying the CSS Regions polyfill features.

• basic css syntax
• basic CSSOM features

Describe the polyfill, use cases and limitations.
Link to the landing page / github repo.

You do not mention IE at all. Is support never ever desired? What are the impediments of supporting IE11 for example?

Investigate using a smarter CSS parser like prefix free does (checking only where flow-from or flow-into is being called and altering them https://github.com/LeaVerou/prefixfree/blob/gh-pages/prefixfree.js) and make the parsing faster