WebKit Bugzilla
New
Browse
Search+
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
NEW
41047
Unify three methods to decide whether a renderer should be created
https://bugs.webkit.org/show_bug.cgi?id=41047
Summary
Unify three methods to decide whether a renderer should be created
Nikolas Zimmermann
Reported
2010-06-23 00:14:20 PDT
We currently have three code paths doing decisions on whether a renderer should be created/destroyed: - Node::rendererIsNeeded(RenderStyle*) - decide whether a Node need a renderer based on RenderStyle information (display() != NONE, etc.) - Node::childShouldCreateRenderer(Node*) - decide whether a children of a certain element should get a renderer - RenderObject::isChildAllowed() - checks whether a new renderer can be appended, if not the renderer is destroyed again (see createRendererIfNeeded()) These code paths should ideally be unified.
Attachments
Add attachment
proposed patch, testcase, etc.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug