WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
157076
Refactor findExplodedTextNodeAtPoint to move core functionality in RenderBlockFlow
https://bugs.webkit.org/show_bug.cgi?id=157076
Summary
Refactor findExplodedTextNodeAtPoint to move core functionality in RenderBloc...
Enrica Casucci
Reported
2016-04-27 10:11:47 PDT
Moving the core functionality to RenderBlockFlow will allow its use from WK2.
Attachments
Patch
(8.56 KB, patch)
2016-04-27 13:59 PDT
,
Enrica Casucci
simon.fraser
: review+
buildbot
: commit-queue-
Details
Formatted Diff
Diff
Archive of layout-test-results from ews123 for ios-simulator-wk2
(709.75 KB, application/zip)
2016-04-27 14:50 PDT
,
Build Bot
no flags
Details
View All
Add attachment
proposed patch, testcase, etc.
Enrica Casucci
Comment 1
2016-04-27 13:59:51 PDT
Created
attachment 277533
[details]
Patch
WebKit Commit Bot
Comment 2
2016-04-27 14:01:54 PDT
Attachment 277533
[details]
did not pass style-queue: ERROR: Source/WebCore/rendering/RenderBlockFlow.h:397: The parameter name "point" adds no information, so it should be removed. [readability/parameter_name] [5] ERROR: Source/WebCore/rendering/RenderBlockFlow.cpp:3363: Should have only a single space after a punctuation in a comment. [whitespace/comments] [5] ERROR: Source/WebCore/rendering/RenderBlockFlow.cpp:3405: Should have only a single space after a punctuation in a comment. [whitespace/comments] [5] Total errors found: 3 in 4 files If any of these errors are false positives, please file a bug against check-webkit-style.
Simon Fraser (smfr)
Comment 3
2016-04-27 14:26:55 PDT
Comment on
attachment 277533
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=277533&action=review
Please address the style bot issues.
> Source/WebCore/rendering/RenderBlockFlow.cpp:3380 > + while (nextChild && nextChild->isFloatingOrOutOfFlowPositioned()) > + nextChild = nextChild->nextSiblingBox();
Why doesn't this do the child->style().visibility() != WebCore::VISIBLE check?
> Source/WebCore/rendering/RenderBlockFlow.h:397 > + WEBCORE_EXPORT Node* findClosestTextAtAbsolutePoint(const FloatPoint& point);
Being a function on a Renderer, this should return a RenderText, not a Node. The caller can get the node.
Build Bot
Comment 4
2016-04-27 14:50:19 PDT
Comment on
attachment 277533
[details]
Patch
Attachment 277533
[details]
did not pass ios-sim-ews (ios-simulator-wk2): Output:
http://webkit-queues.webkit.org/results/1230528
New failing tests: compositing/contents-scale/incremental-change.html
Build Bot
Comment 5
2016-04-27 14:50:23 PDT
Created
attachment 277537
[details]
Archive of layout-test-results from ews123 for ios-simulator-wk2 The attached test failures were seen while running run-webkit-tests on the ios-sim-ews. Bot: ews123 Port: ios-simulator-wk2 Platform: Mac OS X 10.11.4
Enrica Casucci
Comment 6
2016-04-27 15:14:50 PDT
(In reply to
comment #3
)
> Comment on
attachment 277533
[details]
> Patch > > View in context: >
https://bugs.webkit.org/attachment.cgi?id=277533&action=review
> > Please address the style bot issues. > > > Source/WebCore/rendering/RenderBlockFlow.cpp:3380 > > + while (nextChild && nextChild->isFloatingOrOutOfFlowPositioned()) > > + nextChild = nextChild->nextSiblingBox(); > > Why doesn't this do the child->style().visibility() != WebCore::VISIBLE > check?
> Don't know the answer.
> > Source/WebCore/rendering/RenderBlockFlow.h:397 > > + WEBCORE_EXPORT Node* findClosestTextAtAbsolutePoint(const FloatPoint& point); > > Being a function on a Renderer, this should return a RenderText, not a Node. > The caller can get the node.
Done.
Enrica Casucci
Comment 7
2016-04-27 16:52:55 PDT
Committed revision 200162.
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