RESOLVED FIXED160196
Typo in StyleSharingResolver.cpp
https://bugs.webkit.org/show_bug.cgi?id=160196
Summary Typo in StyleSharingResolver.cpp
Emilio Cobos Álvarez (:emilio)
Reported 2016-07-26 06:06:05 PDT
Not a huge deal, just noticed it. Not sure how to test it though.
Attachments
Patch (1.66 KB, patch)
2016-07-26 06:17 PDT, Emilio Cobos Álvarez (:emilio)
no flags
Patch (1.60 KB, patch)
2017-07-05 11:58 PDT, Emilio Cobos Álvarez
no flags
Patch (1.59 KB, patch)
2017-07-05 11:59 PDT, Emilio Cobos Álvarez
no flags
Emilio Cobos Álvarez (:emilio)
Comment 1 2016-07-26 06:17:28 PDT
Darin Adler
Comment 2 2016-07-26 16:00:31 PDT
Comment on attachment 284587 [details] Patch Clearly a correct change and likely valuable. Antti, Jer, any insight into what the symptom will be here?
Antti Koivisto
Comment 3 2016-07-28 00:40:49 PDT
> Clearly a correct change and likely valuable. Antti, Jer, any insight into > what the symptom will be here? It could cause inappropriate style sharing (and so wrong style being applied) from the full screen element to some other element. Good find.
Darin Adler
Comment 4 2016-07-28 08:54:47 PDT
(In reply to comment #3) > > Clearly a correct change and likely valuable. Antti, Jer, any insight into > > what the symptom will be here? > > It could cause inappropriate style sharing (and so wrong style being > applied) from the full screen element to some other element. Good find. Sorry, what I meant to say was, can we figure out how to use this information to help us construct a test case?
Antti Koivisto
Comment 5 2016-07-28 10:36:06 PDT
> Sorry, what I meant to say was, can we figure out how to use this > information to help us construct a test case? It would involve inserting an element that is otherwise identical to the full screen element (in full screen mode) so the style gets copied. This is likely to be somewhat tricky. I assume there is some sort of non-CSS styling in full screen elements that would result in observable differences (since these tests exist).
Emilio Cobos Álvarez
Comment 6 2017-07-04 22:10:40 PDT
*** Bug 174147 has been marked as a duplicate of this bug. ***
Emilio Cobos Álvarez
Comment 7 2017-07-04 22:12:46 PDT
Comment on attachment 284587 [details] Patch Antti, do you think this is worth landing? I think it is, and I remember spending a fair amount of time trying to test this without success (though I could try again I guess). The ChangeLog entry is suboptimal (heh, was my very first try). I can probably send a new patch if you want.
WebKit Commit Bot
Comment 8 2017-07-05 01:50:03 PDT
Comment on attachment 284587 [details] Patch Rejecting attachment 284587 [details] from commit-queue. Failed to run "['/Volumes/Data/EWS/WebKit/Tools/Scripts/webkit-patch', '--status-host=webkit-queues.webkit.org', '--bot-id=webkit-cq-02', 'validate-changelog', '--check-oops', '--non-interactive', 284587, '--port=mac']" exit_code: 1 cwd: /Volumes/Data/EWS/WebKit /Volumes/Data/EWS/WebKit/Source/WebCore/ChangeLog neither lists a valid reviewer nor contains the string "Unreviewed" or "Rubber stamp" (case insensitive). Full output: http://webkit-queues.webkit.org/results/4055293
Antti Koivisto
Comment 9 2017-07-05 01:51:03 PDT
Sure, please land it. ChangeLog needs some fixes to get through the commit queue.
Emilio Cobos Álvarez
Comment 10 2017-07-05 11:58:28 PDT
Emilio Cobos Álvarez
Comment 11 2017-07-05 11:59:39 PDT
WebKit Commit Bot
Comment 12 2017-07-05 12:58:52 PDT
Comment on attachment 314632 [details] Patch Clearing flags on attachment: 314632 Committed r219147: <http://trac.webkit.org/changeset/219147>
WebKit Commit Bot
Comment 13 2017-07-05 12:58:53 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.