| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
(These are failures not caused by the scrollbars change)
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12514 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
Currently there's a scrollbars change which we have reverted in our
local WebKit because it broke layout tests. These rebaselines correct
for the scrollbars change.
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12512 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/40088
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12507 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
server.upload-dirs field is not in lighttpd.conf, failure some
layout tests that do POST. Without that path, Lighttpd fails to
save upload data and return HTTP response 413.
Review URL: http://codereview.chromium.org/53070
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12504 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
This will require updating a couple scripts. I've updated run_webkit_tests.
I think jonc and sandholm's scripts will need updating once this is committed.
Also, while I'm modifying run_webkit_tests.py, re-adds --num-test-shells argument as I'm trying to make it work.
Review URL: http://codereview.chromium.org/49030
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12496 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
| |
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12495 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/42607
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12488 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/45056
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12487 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The solution is to add a user-defined identifier to UploadData.
If that identifier is set, and if the request method is POST,
then HttpCache will enable caching for the response. (The cache
key will be a composition of the identifier and the URL.) A
subsequent POST request to the same URL with the same identifier
will "hit" the previously generated cache entry. Reuse from the
cache is subject to all of the standard rules.
For reference, here are the corresponding net changes:
http://codereview.chromium.org/52028
Here are the corresponding WebKit changes:
http://trac.webkit.org/changeset/41919
BUG=2636
R=sky
Review URL: http://codereview.chromium.org/52040
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12485 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
Writing a bitmap to the clipboard is a rather slow operation, as it involves piping it over IPC and then converting it to a PNG.
Review URL: http://codereview.chromium.org/42592
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12482 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/49031
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12478 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=8786
Review URL: http://codereview.chromium.org/42587
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12474 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
LayoutTests/fast/encoding/char-decoding.html in platform/chromium-{win,mac}/fast/encoding. Somehow, they're baselined to have a bunch of 'FAIL' lines. The expected result in the test directory (LayoutTests/fast/encoding/char-decoding-expected.txt) shouldwork for all the platforms. It's platform-independent. BUG=9247
Review URL: http://codereview.chromium.org/42583
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12471 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/53042
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12455 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
--run-part=x:y runs the xth part out of yth.
X is 1 based.
example, to run all the tests in 3 runs :
--run-part=1:3
--run-part=2:3
--run-part=3:3
Review URL: http://codereview.chromium.org/42170
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12448 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
for the rebaselining is the error message which is the same on all
platforms.
Review URL: http://codereview.chromium.org/53052
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12446 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The problem was that the security token in V8 was set to the string
"null" for all data urls. Therefore, the access check succeeded. The
cause of the regression was that securityOrigin's toString
implementation was changed in WebKit to return "null" instead of
String().
R=kasperl@chromium.org
TBR=scherkus@chromium.org
Review URL: http://codereview.chromium.org/53049
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12444 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
| |
Add an empty line at the end of the README file.
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12443 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/47009
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12442 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
This is almost the same change as <http://codereview.chromium.org/39252/show>, which caused a build break on a Linux buildbot while compiling my new template function in "chrome/common/render_messages.h".
Even though I was not able to reproduce the build errors on my Linux box, I removed this function and use the int type in my IPC message 'ViewMsg_SetTextDirection'.
BUG=1845
Review URL: http://codereview.chromium.org/42495
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12434 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
Nico Weber <nicolasweber@gmx.de>.
Review URL: http://codereview.chromium.org/42561
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12433 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
of test_shell_tests.
Fixes following valgrind warning:
380 bytes in 9 blocks are possibly lost in loss record 331 of 423
at operator new(unsigned int) vg_replace_malloc.c:230
by std::string::_Rep::_S_create(unsigned int, unsigned int, std::allocator<char> const&) (in libstdc++.so.6.0.9)
by (within libstdc++.so.6.0.9)
by std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(char const*, std::allocator<char> const&) (in libstdc++.so.6.0.9)
by CommandLine::CommandLine(int, char const* const*) src/base/command_line.cc:96
by CommandLine::Init(int, char const* const*) src/base/command_line.cc:177
by main src/webkit/tools/test_shell/run_all_tests.cc:57
Review URL: http://codereview.chromium.org/45041
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12429 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the autofill popup.
Pressing up would not trigger that behavior.
This happened because the default processing of the up arrow key is to move the caret to the beginning of the text input.
Showing the autofill is done as a posted task.
Because the caret was not at the end of the text-field by the time that task got executed, the popup would not show.
The fix is to not default process the up/down arrow key messages when an autofill popup will be shown.
Also fixed the WebViewImpl::HideAutoCompletePopup (harmless bug, calling it twice would cause it to hide the already hidden popup).
BUG=6437
TEST=Make sure up/down arrow keys trigger the autofill menu correctly (especially when there is already text in the text-field). Make sure autofill still works as expected.
Review URL: http://codereview.chromium.org/53017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12428 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/49025
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12419 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
TBR=nsylvain
Review URL: http://codereview.chromium.org/53032
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12416 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I modified this test upstream so we could do the file drag/drop into
an iframe. There are still font size differences and the image that
gets dropped in the iframe has a size of 0x0 because it hasn't loaded
by the time the render tree is snapshotted. It works fine in chrome
when run manually, so just rebaseline with the 0x0 image size (the
test still passes: it drops the image).
invalid-syntax-for-function.html:
The exception text changed from saying line 1 to line 2 (exception in a inline body onload handler). Not sure why it changed, but seems harmless.
Review URL: http://codereview.chromium.org/53016
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12405 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/53021
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12399 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the Mac test_shell. Once the changes to
WebKit/WebCore/platform/chromium/PopupMenuChromium* have
been upstreamed (then landed in our tree), we can enable
them in test_shell.
The WebKit part is contained in this bug:
https://bugs.webkit.org/show_bug.cgi?id=24692
BUG=5095 (http://crbug.com/5095)
Review URL: http://codereview.chromium.org/48149
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12382 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
on Windows.
This is the same as Windows Safari, but on the mac it's just courier.
Review URL: http://codereview.chromium.org/42547
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12381 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
LayoutTests/http/tests/xmlhttprequest/redirect-cross-origin-post.html
The crash happens in simple_resource_loader_bridge.cc, there is a
case when MaybeUpdateUploadProgress is posted as a task and in the
queue while a redirect response by the server cancels the upload.
Leaving request_->get_upload() returns NULL, and of cource using of
the pointer failes.
Review URL: http://codereview.chromium.org/50077
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12379 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
| |
Before submitting, I'll add DEPS with corresponding WebKit rev (see http://codereview.chromium.org/52007)
Review URL: http://codereview.chromium.org/45035
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12377 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
we don't know why.
The decision to rebaseline came from:
2009/3/20 Brett Wilson <brettw@google.com>
Actual matches IE very closely, whereas expected doesn't. I had Idan
check this and he says the new one is better, so we should rebaseline.
Even though it is called "ATSUI," this test really tests some basic
features of complex text that will apply to any font system (and I had
to do some work to make ours look good). So it's important we run this
test.
Review URL: http://codereview.chromium.org/51005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12368 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
the code triggering this was just checking that the focused element before and after processing the event was the same.
We need to do a hit test to ensure the click is really on the text field, otherwise in cases where clicking somewhere in the page does not change the focus, we would bogusly bring up the autofill popup.
BUG=8627
TEST=Ensure autocomplete popup still works as expected: when entering text, when using up/down arrows, when clicking selected text field. Also ensures the scenario from the bug does not trigger the popup.
Review URL: http://codereview.chromium.org/50038
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12367 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
| |
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12363 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/45031
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12362 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
flag):
- Add new devtools IPC message
- Expose WebView's hit target
- Refactor dom_agent interaction not to send information known to client
- Collect incoming messages on the client until frontend is loaded
- Add Inspect Element scenario into the devtools_host_stub
Review URL: http://codereview.chromium.org/45022
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12355 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
| |
in the event listener wrapper code.
Review URL: http://codereview.chromium.org/42557
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12353 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
9177.
Already skipped under purify.
Review URL: http://codereview.chromium.org/42558
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12351 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
now that we're valgrinding.
Review URL: http://codereview.chromium.org/42471
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12350 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/53003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12349 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
results.
Review URL: http://codereview.chromium.org/42262
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12347 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
TBR=ojan
Review URL: http://codereview.chromium.org/42552
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12345 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
the title in the task manager, and show an infobar when a page's workers die.
I also cleaned up the code in RenderView which creates a window and widget, since when I originally wrote it I wasn't aware of RenderViewHost::FromID.
Review URL: http://codereview.chromium.org/45025
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12335 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
TBR=ojan
Review URL: http://codereview.chromium.org/42545
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12331 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
TBR=ojan
Review URL: http://codereview.chromium.org/52035
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12327 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The encoding parameter got dropped from Workers (r41871) so
drop it through the whole stack.
The upstream WorkerContextExecutionProxy has trackEvent with a lower
case t, but we pull in the wrong header in some places so make
both headers match.
Review URL: http://codereview.chromium.org/42538
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12326 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/52027
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12320 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/42534
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12315 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/42533
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12313 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
https://bugs.webkit.org/show_bug.cgi?id=24526
and so is being rebaselined too, as were the tests commited in rev 12295.
Review URL: http://codereview.chromium.org/42529
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12311 0039d316-1c4b-4281-b951-d872f2087c98
|