Quantcast
Channel: HTML Renderer
Viewing all articles
Browse latest Browse all 693

Commented Issue: Enhancement proposals [3580]

$
0
0
I have used the HTML panel for a little test.
I have already submitted code that supports classnames a little better.
 
I propose that the DOM elements are exposed, so the user can create html nodes with html fragments, like
new CssBox("<div class=\"xx\">sample</div>")
 
And then attaching the new node to the existing tree.
 
When doing this, you will notice that the current method of pusing inherited values onto child elements,
wont't work, because you attach the node after the style has been applied.
 
Instead, the attributes should be nullable, and default null. Whenever encountering a null value,
the parents value should be used instead. Using this approach, you can freely move items in the tree, and they will
render as expected.
 
I can do some of the work, if you like.
Comments: +1 to the DOM being exposed ... I have exposed it in my project ... but it is such a pain to update every time the HTML Renderer is updated :(... BTW I mainly exposed it so that i could get the bounds for each html item. Kris

Viewing all articles
Browse latest Browse all 693

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>