WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED DUPLICATE of
bug 76459
73753
Move shouldLayoutFixedElementsRelativeToFrame to Page.cpp
https://bugs.webkit.org/show_bug.cgi?id=73753
Summary
Move shouldLayoutFixedElementsRelativeToFrame to Page.cpp
Fady Samuel
Reported
2011-12-03 13:02:23 PST
Move shouldLayoutFixedElementsRelativeToFrame to Page.cpp
Attachments
Patch
(10.71 KB, patch)
2011-12-03 13:04 PST
,
Fady Samuel
eric
: review-
gustavo.noronha
: commit-queue-
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Fady Samuel
Comment 1
2011-12-03 13:04:32 PST
Created
attachment 117772
[details]
Patch
Fady Samuel
Comment 2
2011-12-03 13:07:20 PST
I don't know if this is better in Page or as a Setting? I've put it in Page until someone can give me a good reason to make this a Setting
Collabora GTK+ EWS bot
Comment 3
2011-12-03 13:56:51 PST
Comment on
attachment 117772
[details]
Patch
Attachment 117772
[details]
did not pass gtk-ews (gtk): Output:
http://queues.webkit.org/results/10734347
Darin Adler
Comment 4
2011-12-03 15:18:39 PST
Comment on
attachment 117772
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=117772&action=review
> Source/WebCore/page/FrameView.cpp:1397 > + bool shouldLayoutFixedElementsRelativeToFrame = frame()->page() ? frame()->page()->shouldLayoutFixedElementsRelativeToFrame(): false;
&& might be more readable here than ? :
> Source/WebCore/page/Page.cpp:687 > + if (m_mainFrame && m_mainFrame->document()->renderer()) > + m_mainFrame->document()->renderer()->setNeedsLayout(true);
Don’t we have to do this for subframes too?
WebKit Review Bot
Comment 5
2011-12-03 17:54:06 PST
Comment on
attachment 117772
[details]
Patch
Attachment 117772
[details]
did not pass chromium-ews (chromium-xvfb): Output:
http://queues.webkit.org/results/10732339
New failing tests: svg/custom/linking-uri-01-b.svg
Fady Samuel
Comment 6
2011-12-03 19:43:27 PST
Comment on
attachment 117772
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=117772&action=review
>> Source/WebCore/page/FrameView.cpp:1397 >> + bool shouldLayoutFixedElementsRelativeToFrame = frame()->page() ? frame()->page()->shouldLayoutFixedElementsRelativeToFrame(): false; > > && might be more readable here than ? :
Sure, I'll do this in a patch refresh.
>> Source/WebCore/page/Page.cpp:687 >> + m_mainFrame->document()->renderer()->setNeedsLayout(true); > > Don’t we have to do this for subframes too?
This setting has no impact on subframes or at least should have no impact on subframes (There might be a bug here that I need to test for) because frameScaleFactor == 1 for subframes. I have to confirm this isn't broken in a layout test.
Eric Seidel (no email)
Comment 7
2011-12-21 13:30:08 PST
Comment on
attachment 117772
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=117772&action=review
Seems reasonable to me, but loks like the EWS bots strongly disagree. Please upload a new patch which passes EWS. :)
> Source/WebCore/ChangeLog:10 > + of frame because it's a no-op on subframes. This is a page-level property. To > + reduce confusion and to save a few bytes, it has been moved to Page.
Bytes don't really matter on FrameView. :)
Fady Samuel
Comment 8
2012-01-25 19:21:31 PST
*** This bug has been marked as a duplicate of
bug 76459
***
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