WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
166837
Support webkit-test-runner key-value pairs in http tests in DumpRenderTree
https://bugs.webkit.org/show_bug.cgi?id=166837
Summary
Support webkit-test-runner key-value pairs in http tests in DumpRenderTree
Antoine Quint
Reported
2017-01-09 04:17:20 PST
With
https://bugs.webkit.org/show_bug.cgi?id=149812
, we added support for webkit-test-runner key-value pairs in http tests in WebKitTestRunner. We also need this to work with DumpRenderTree / WebKit1 so that we can get legacy media controls tests to work when modern media controls are on by default (see
https://bugs.webkit.org/show_bug.cgi?id=165668
).
Attachments
Patch
(4.74 KB, patch)
2017-01-09 05:18 PST
,
Antoine Quint
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1
2017-01-09 04:17:52 PST
<
rdar://problem/29925855
>
Antoine Quint
Comment 2
2017-01-09 05:18:17 PST
Created
attachment 298343
[details]
Patch
Alexey Proskuryakov
Comment 3
2017-01-09 09:42:40 PST
The purpose of WKTR key value pairs is to add settings that require restarting WebContent process, and so it's by definition impossible to implement for DumpRenderTree. The fact that it's implementable tells me that this was the wrong mechanism to enable modern media controls in tests. Why didn't a JS call work?
WebKit Commit Bot
Comment 4
2017-01-09 11:35:49 PST
Comment on
attachment 298343
[details]
Patch Clearing flags on attachment: 298343 Committed
r210517
: <
http://trac.webkit.org/changeset/210517
>
WebKit Commit Bot
Comment 5
2017-01-09 11:35:54 PST
All reviewed patches have been landed. Closing bug.
Antoine Quint
Comment 6
2017-01-10 07:30:26 PST
(In reply to
comment #3
)
> The fact that it's implementable tells me that this was the wrong mechanism > to enable modern media controls in tests. Why didn't a JS call work?
The value of using a WKTR key-value pair is that the setting can be set prior to any media element being created inside the test. Using a JS call would have required for all media tests that wish to set a different value than the default to dynamically create the media element after calling JS to change it.
Alexey Proskuryakov
Comment 7
2017-01-10 14:19:11 PST
My understanding is that the markup for the media element won't be parsed until preceding JS executes. In other words, this should work due to the way HTML parser works, (and it works that way because of document.write()): <script> internals.enableModernMediaControls(); </script> <video>...</video>
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