| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This helps the Window.onLoad fires at correct time. Since Android
implements the video playing using Java's full screen VideoView, nothing
happens before the user clicks the play button. So need to fake some
event change.
Current prepareToPlay also fakes event change before real video playing.
issue: 3346048
Change-Id: I5afa1a2ecf920b23f902d0ac3916223a6cf8ac0c
|
|\ \ \ \
| |_|_|/
|/| | | |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Also record scroll point and view scales when webcore scroll offset
is changed.
This will help history navigation and browser restoration.
issue: 2819082
Change-Id: I3e59806d8110127ed9a2e32b917c4176ffa6bf73
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Use the nav cache to determine if a given
coordinate corresponds to a plugin.
Requires a companion change in frameworks/base
bug:3331323
Change-Id: Ica8291bf0dfaaae7c0918b1a685c07fe756d9328
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
Don't just use text/plain or application/octet-stream,
this matches the old stack.
Fix for bug 2981069
Change-Id: I1b5edf0e60e7c7012f4143906ec926227edcf927
|
| |
| |
| |
| |
| |
| |
| | |
The old code would only return the correct value after a
background thread had been running.
Change-Id: I79c0be8606b005b6a18aa83f5b91891709d4e0f5
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If the eventHandler says the key was handled, don't
allow the contentEditable test to set handled to false.
bug:3351951
Change-Id: I0dbe956e8983c16e738760e3b159d1353cc3eddd
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
* changes:
Resolve MIME types for CacheResult in the same way as WebResponse.
Hook up CacheManager for the Chromium HTTP stack
|
| | | |
| | | |
| | | |
| | | | |
Change-Id: I972bbdabc8491a94eabd676dd13f09fcccb6ba88
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Requires a corresponding change in frameworks/base
https://android-git.corp.google.com/g/87939
Bug: 3270236
Change-Id: I31a640de86d6fad00eb8b71784e0ee9136ab1174
|
|/ / /
| | |
| | |
| | | |
Change-Id: I92ac985aba6780bc00f6dfbdca7e72f645b03580
|
|\ \ \
| |_|/
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is the CL in WebKit side and it needs the framwork CL:
https://android-git.corp.google.com/g/#change,89630
Notice some changes touch open source WebKit's code, so b/3351313 is filed
to keep track of that.
Change-Id: I0ac5d75c4a90f14afeb2e3fc2dc5b1c437c631f8
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is no longer needed as we are taking a different approach to auto login.
Change-Id: If665c740d958c4947527ce32e2b7f858736cac2b
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The problem is if a request is just started as the browser (or a tab)
is closed. That can give delete the scoped_refptr before the
refcount is increased on the IO thread.
Refcounted objects should not be passed as raw pointers between
threads.
Change-Id: I57a9b30f5fdfef3c6d45b81ea59a61f96b09e6ae
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
Part of fix for bug 2862096
Change-Id: Iabef7251b867b0c8bbf81147b08c76e7ef723d00
|
| |/
|/|
| |
| | |
This reverts commit 5bc439a352fa4a52aa5be1eab0dc72420f40d49f.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Bug:3344162
Requires a change in frameworks/base.
Change-Id: Id6fddcb2f179695998ef9372b8bca36bebbb54a3
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
Bug:3344795
Change-Id: I8c4bb2aa3c105da1d08260daa9a9d11d39de7840
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The cx, cy locals are later stored as part of the
best character found. They must always be computed
so that the best state can compare with the test
state.
bug:3339016
Change-Id: I4cbb791dc8d3836b027c6a9088dc3a59031c40b9
|
|\ \ \ \
| |_|/ /
|/| | | |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
setBridge calls adoptRef on the bridge and the stack object deletes the bridge.
Deleted memory is no good.
Change-Id: I80c5f614da604c0362530a54ff04b892d96ef6b1
|
|\ \ \
| | | |
| | | |
| | | | |
honeycomb
|
| | |/
| |/|
| | |
| | |
| | |
| | | |
Bug:3341272
Change-Id: Ibf00b2cb5a2c34eed9e5ac0355b59f8507ade446
|
|\ \ \
| |_|/
|/| | |
|
| |/
| |
| |
| |
| | |
Bug:3328480
Change-Id: I47a7df3e5ffb043e6162b661a6de3a837d141c88
|
| |
| |
| |
| |
| |
| |
| | |
Part of fix for bug 2862096
Fix for bug 3280996
Change-Id: I82d872aff834524fb105f42e83eee580d6c98c0b
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This change helps page navigation, since the restored scale
is accurate.
This change has a corresponding change in frameworks/base.
https://android-git.corp.google.com/g/#change,88121
issue: 3225233
Change-Id: I7e5601e8412e8b81e7f32c9ffb9e6c114db95169
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Use adoptRef when creating a new bridge item. Use
toRenderBoxModelObject instead of toRenderBox as RenderInlines have layers.
Bug: 3321493
Change-Id: I4283681eba961aedaa8d80bfdfb3d1a468aab1ac
|
|\ \ \
| |_|/
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This helps scrolling to a page#anchor link as shown in the bug.
Not sure I understand the reason to have that setting at the first place.
issue: 3225233
Change-Id: If2960d3c77be94b150e138a534007708f025dbad
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Iad96314e,Ic978944b,Iea1a5a55,Id22f7f0c,Ia1a391a9,Ic4642c38,I561d89dc,Ia102dea1 into honeycomb
* changes:
Merge Chromium at 9.0.597.55: Move formsSeen call to IO thread.
Merge Chromium at 9.0.597.55: Remove URLRequest forward declaration.
Merge Chromium at 9.0.597.55: Merge 67599. (2/2)
Merge Chromium at 9.0.597.55: Merge r67599 (1/2)
Merge Chromium at 9.0.597.55: Merge r67192
Merge Chromium at 9.0.597.55: Add DnsCertChecker to constructor
Merge Chromium at 9.0.597.55: Autofill: Merge r66860
Merge Chromium at 9.0.597.55: Autofill: Merge r66850
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When we search the document for forms to be autofilled, we make a URL
request to the AutoFill server to ask it for form field data. With
Chromium r67655, this URL request needs to be made on a Chrome thread.
This is a simple fix for the merge, which blocks until the call
completes.
See http://src.chromium.org/viewvc/chrome?view=rev&revision=67655
Change-Id: Iad96314e4ecb66ee7e65c1ef846709e9c41b0e2e
|
| | | |
| | | |
| | | |
| | | | |
Change-Id: Ic978944b7a4e0bdda4ab09a18234456098ad26ca
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This needed a bit of work so I've split into two commits.
This is part 2, where we now need to pass both the field that
was focussed and the form it belongs to. To achieve this I have
a new class that encapsulates the pointers.
Change-Id: Iea1a5a55696c63255bcc57b070116409a2195f4c
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is a slightly tricky merge. This first part is the easy bit.
See http://src.chromium.org/viewvc/chrome?view=rev&revision=67599
Change-Id: Id22f7f0ce0f0b7eca62f39d4e6ae65b9ea1bdcda
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
See http://src.chromium.org/viewvc/chrome?view=rev&revision=67192
Change-Id: Ia1a391a9e7634e86e5c3166349befc47841b570e
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
See http://src.chromium.org/viewvc/chrome?view=rev&revision=66985
Change-Id: Ic4642c38646b94fb6db9e839a671cd335f9d5c6b
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
See http://src.chromium.org/viewvc/chrome?view=rev&revision=66860
Change-Id: I561d89dcc060af7f3e0b975e4a940c7de63d89d4
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Autofill: Prefer maxLength to size attribute for form filling
heuristics.
See http://src.chromium.org/viewvc/chrome?view=rev&revision=66850
Change-Id: Ia102dea1c861474e878639b91288e6845d7250ef
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The algorithm that analyzes cursor rings in pictures
stores the changes to the canvas (e.g. push layer, pop)
but it turns out that bitmaps may have push/pop
pairs around them that don't represent a state change.
Remove the push/pop pairs around bitmaps when creating
the cursor region stack.
bug:3299913
bug:3329011
Change-Id: I14e0508285821e2723ff460e6b09faccb44f4565
|
|\ \ |
|