Bug 187986
| Summary: | [Curl] Add test for the read/write buffer works well by changing its size. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Basuke Suzuki <basuke> |
| Component: | Platform | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | ||
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Basuke Suzuki
It is no practical reason for small size of buffer, but it simulates the situation when bigger size of data is going to be out. It must be the test case for the buffering system using background thread.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Basuke Suzuki
Dydz said in IRC:
<https://trac.webkit.org/wiki/Exposing%20WebKit%20internals%20for%20Layout%20Tests>
The wiki is outdated and more of a story :/ You can can access any WebCore setting (defined in <https://trac.webkit.org/browser/trunk/Source/WebCore/page/Settings.yaml?rev=234091#L7>) in a layout tests using syntax of the form window.internals.settings.setMinimumFontSize(5)
You can also expose WebCore functionality by adding a new function to the window.internals object by adding the functionl to the IDL at <https://trac.webkit.org/browser/trunk/Source/WebCore/testing/Internals.idl?rev=234091#L123> and then implementing the function in WebCore/testing/Internals.{h, cpp}
window.internals is only available when running WebKitTestRunner and DumpRenderTree