| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently search results are cleared when user rotates
pdf document. As a result, the forward/backward buttons in
find bar do not work if user rotates pdf document after
finding some text in the document.
This happens because |find_results_| is cleared in the method
InvalidateAllPages(), which is called after rotation.
This patch introduces a new method to restore find results state
after invalidate operation is done. New find operation is done
to ensure rects are correctly identified for search results and
correct region is highlighted on pressing forward/backward buttons
in find bar.
BUG=389782
Review URL: https://codereview.chromium.org/555803002
Cr-Commit-Position: refs/heads/master@{#298083}
|
|
|
|
|
|
|
|
|
|
|
|
| |
out_of_process_pdf.cc
This moves the logic to handle the ctrl+a keyboard event into the pdf.js container page, sending a message to the plugin to select all the text. This ensures that the event is handled, even if the plugin element doesn't have focus in the document.
BUG=419986
Review URL: https://codereview.chromium.org/615853003
Cr-Commit-Position: refs/heads/master@{#297998}
|
|
|
|
|
|
| |
Review URL: https://codereview.chromium.org/617163002
Cr-Commit-Position: refs/heads/master@{#297649}
|
|
|
|
|
|
|
|
|
|
|
| |
loop should break after match as values are getting reset to empty
rect after match.Changes done so that loop breaks after match.
BUG=417621
Review URL: https://codereview.chromium.org/603903002
Cr-Commit-Position: refs/heads/master@{#297138}
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Memory for WriteInto() should be greater than the url length,
As in the WriteInto() it reserve the memory of size 'length_with_null'
and then resize it to "length_with_null-1'
Chnage done to give memory 1 greater than the url length size.
BUG=417732
Review URL: https://codereview.chromium.org/599373003
Cr-Commit-Position: refs/heads/master@{#297102}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
of https://codereview.chromium.org/457873003/)
Reason for revert:
No longer needed.
Original issue's description:
> PDF: Add some CHECKS to help debug a crash.
>
> BUG=402035
>
> Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=289822
TBR=gene@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=402035
Review URL: https://codereview.chromium.org/607743005
Cr-Commit-Position: refs/heads/master@{#297067}
|
|
|
|
|
|
|
|
|
|
|
| |
The default modifier key on Mac is Command, but that conflicts with
the forward and backward keys.
BUG=111232,417902
Review URL: https://codereview.chromium.org/606933002
Cr-Commit-Position: refs/heads/master@{#297033}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently there are no keyboard shortcuts to rotate pdf
documents. This patch adds the following keyboard shortcuts
to rotate pdf documents :
Rotate counterclockwise : Control + [
Rotate clockwise : Control + ]
BUG=111232
Review URL: https://codereview.chromium.org/581913003
Cr-Commit-Position: refs/heads/master@{#295757}
|
|
|
|
|
|
|
|
|
|
|
| |
Speculative fix for 415307. CF will confirm.
The stack trace for that bug indicates an attempt to index by -1, which is consistent with no visible page.
BUG=415307
Review URL: https://codereview.chromium.org/560133004
Cr-Commit-Position: refs/heads/master@{#295421}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
than a double.
In the in-process PDF plugin when checking the argument type of kJSSetZoomLevel
calls to the plugin we would check if the argument is a double. But it may be
an int and we really want to check if it's a number. This probably worked in
the past by chance and broke when we switched to using gin to implement JS
bindings for Pepper.
BUG=413525
Review URL: https://codereview.chromium.org/569403004
Cr-Commit-Position: refs/heads/master@{#295008}
|
|
|
|
|
|
| |
Review URL: https://codereview.chromium.org/571843002
Cr-Commit-Position: refs/heads/master@{#294995}
|
|
|
|
|
|
|
|
|
|
| |
This regressed in r294564.
BUG=413850
Review URL: https://codereview.chromium.org/568803004
Cr-Commit-Position: refs/heads/master@{#294854}
|
|
|
|
|
|
|
|
|
|
|
| |
Also format text to match Adobe Reader.
BUG=307523
TEST=Manual, see bug (and duplicates for more examples)
Review URL: https://codereview.chromium.org/566773005
Cr-Commit-Position: refs/heads/master@{#294638}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently links in pdf open on mouse down. This doesn't
give user any chance to cancel the action by moving the mouse
without releasing the click.
This patch adds the fix to make sure pdf opens link on mouse up
and not on mouse down.
BUG=409753
Review URL: https://codereview.chromium.org/553433002
Cr-Commit-Position: refs/heads/master@{#294564}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently context menu for page is shown when right clicked
on links in the pdf. This happens because an empty string is
returned as url to ContextMenuClientImpl::showContextMenu()
from plugin.
The reason for above is that GetLinkAtPosition() isn't passing
a point in page coordinates to GetCharIndex() and GetCharIndex()
expects the point to be in page coordinate. This means that when
the document is zoomed or scrolled and right click is done then
it doesn't work.
This patch updates the point passed to GetCharIndex() to be in
page coordinates by factoring in current position and zoom level.
BUG=148665
Review URL: https://codereview.chromium.org/553453002
Cr-Commit-Position: refs/heads/master@{#294256}
|
|
|
|
|
|
|
|
|
|
|
|
| |
Per msan report, the line in question reads:
if (timer_id == fade_out_timer_id_) {
so initialize fade_out_timer_id_ in the constructor.
BUG=411177
Review URL: https://codereview.chromium.org/557493002
Cr-Commit-Position: refs/heads/master@{#294055}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, destroying a PDFiumPage triggers an Unload() which can result
in an access to other PDFiumPages. But these other pages may already have
been destroyed as a previous element via STLDeleteElements(&pages_).
Instead, unload all pages first, then destroy them all afterwards so that
no access to other pages will be attempted after the destruction of the
first one has begun.
Move the STLDeleteElements() call to the bottom, to make it more closely
mimic the ordering that might occur should pages_ someday be switched
from vector to ScopedPtrVector or similar.
BUG=384365
Review URL: https://codereview.chromium.org/544873002
Cr-Commit-Position: refs/heads/master@{#293800}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Similar to bug 398384, but perform the same bounds check we introduced to
chrome_pdf::CopyImage() in the chrome_pdf::AlphaBlend() function.
Also change the return value from bool to void, since AlphaBlend() always
returns true, and no-one was checking the return value anyways.
BUG=384891
Review URL: https://codereview.chromium.org/544863002
Cr-Commit-Position: refs/heads/master@{#293454}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Layout changes trigger view changes which get sent to the plugin. With the
in process plugin (PDF), the plugin is notified synchronously of the view
change. It then might execute scripts synchronously in the plugin but
scripts are not meant to be executed during layout changes. This change
runs the scripts asynchronously. I tested print preview to ensure that it
still works correctly.
Note that once we remove in-process plugins this won't be an issue because
view changes happen asynchronously out of process (besides the fact that
synchronous script execution is limited to private plugins).
BUG=351636
Review URL: https://codereview.chromium.org/530363002
Cr-Commit-Position: refs/heads/master@{#293256}
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a re-work of palmer's patch at https://codereview.chromium.org/515023002/ which has more context, but comes down to stricter bounds checking.
We also correct an arithmetic bug when copying the image behind a control that is positioned before the origin of the image.
BUG=398384
Review URL: https://codereview.chromium.org/519873002
Cr-Commit-Position: refs/heads/master@{#293213}
|
|
|
|
|
|
|
|
| |
NOTRY=true
Review URL: https://codereview.chromium.org/524433003
Cr-Commit-Position: refs/heads/master@{#292549}
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
PrintPagesAsRasterPDF().
Fixed page passed into FPDFPageObj_NewImgeObj().
BUG=385119
Review URL: https://codereview.chromium.org/485413002
Cr-Commit-Position: refs/heads/master@{#290780}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290780 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=401242
R=thestig@chromium.org
Review URL: https://codereview.chromium.org/484393002
Cr-Commit-Position: refs/heads/master@{#290766}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290766 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If CopyImage is called with src is an empty rectangle (this can happen for
example if one of the resources is not available), then the code ends up trying
to read from null/uninitialized memory. So early out instead in such cases.
BUG=401242
R=thestig@chromium.org
Review URL: https://codereview.chromium.org/465133005
Cr-Commit-Position: refs/heads/master@{#290736}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290736 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds support for "page" feature of open PDF
parameters in OOP PDF.
When page is used as an open PDF parameter, then PDF
should initially be loaded at the page specified by user.
BUG=64309
Review URL: https://codereview.chromium.org/476733003
Cr-Commit-Position: refs/heads/master@{#290529}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290529 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the PDF hasn't loaded.
Original fix:
https://codereview.chromium.org/427723004/
The original fix was reverted, however it actually shouldn't have been because it was mostly correct. This fix is the same as the old one, with an additional change. The call to DidStopLoading() in Instance::DocumentLoadComplete was moved to an earlier part of the function, causing DidStopLoading to be called before the print preview request.
BUG=376969
Review URL: https://codereview.chromium.org/467343003
Cr-Commit-Position: refs/heads/master@{#290010}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290010 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=402035
Review URL: https://codereview.chromium.org/457873003
Cr-Commit-Position: refs/heads/master@{#289822}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289822 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
> Move StringToUpperASCII and LowerCaseEqualsASCII to the base namespace
>
> Convert LowerCaseEqualsASCII to take StringPiece. In the current patch this is
> generally a NOP but will allow me to delete the other 4 variants in a followup
> (wanted to do that separately since that will require more review, since
> callsites will be changed in nontrivial ways).
>
> In some cases, LowerCaseEqualsASCII is called with a WebString, which no
> longer is implicitly converted. I added base::string16(...) around such
> calls to force the right conversion. It happened in these files:
> window_container_type.cc
> savable_resources.cc
> render_view_impl.cc
> blink_ax_tree_source.cc
> password_form_conversion_utils.cc
> translate_helper.cc
> chrome_render_view_observer.cc
> dom_serializer_browsertest.cc
>
> R=jamesr@chromium.org
>
> Review URL: https://codereview.chromium.org/448143008
TBR=brettw@chromium.org
Review URL: https://codereview.chromium.org/474483002
Cr-Commit-Position: refs/heads/master@{#289320}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289320 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Convert LowerCaseEqualsASCII to take StringPiece. In the current patch this is
generally a NOP but will allow me to delete the other 4 variants in a followup
(wanted to do that separately since that will require more review, since
callsites will be changed in nontrivial ways).
In some cases, LowerCaseEqualsASCII is called with a WebString, which no
longer is implicitly converted. I added base::string16(...) around such
calls to force the right conversion. It happened in these files:
window_container_type.cc
savable_resources.cc
render_view_impl.cc
blink_ax_tree_source.cc
password_form_conversion_utils.cc
translate_helper.cc
chrome_render_view_observer.cc
dom_serializer_browsertest.cc
R=jamesr@chromium.org
Review URL: https://codereview.chromium.org/448143008
Cr-Commit-Position: refs/heads/master@{#289312}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289312 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The crash occurs because of a timer dereferencing a null engine pointer.
The crash appears to have occurred due to this patch https://codereview.chromium.org/427583003/
Fix is to cancel all timers when the pdf instance is being torn down before
destroying the engine.
BUG=403036
Review URL: https://codereview.chromium.org/462283002
Cr-Commit-Position: refs/heads/master@{#289218}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289218 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
TBR=sky
Review URL: https://codereview.chromium.org/448853002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@288085 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The instance owns the engine via its engine_ scoped_ptr, so if the engine is
being destroyed via the scoped_ptr destructor, it may not be safe to access
anything in the instance since the instance may be partially destroyed. Instead,
destroy the engine as the first step in the process so the instance is still
intact.
BUG=392956
Review URL: https://codereview.chromium.org/427583003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@287955 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
scales.
Reason for the bug is painting code in the pdf plugin which converts back and forth from pixels to DIP
and back to pixels causing us to draw over the scrollbars. Division and multiplication with fractional scales
Is a lossy operation.
BUG=399150
TEST=Tested manually with fractional scales on Windows.
Review URL: https://codereview.chromium.org/437873002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@287952 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=397624
Review URL: https://codereview.chromium.org/431303002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@287520 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
There are some OS_NACL ifdefs in pdf/{instance.cc/out_of_process_instance.cc}.
I assume these are from long ago when we tried to get PDF running in NaCl but
I believe that at present many more changes would be required to get it
running in NaCl again so we might as well remove these.
Review URL: https://codereview.chromium.org/424763008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@286927 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the response is too long to return in the caller-supplied buffer,
truncate it to fit per the description of the app_response method in
third_party/pdfium/fpdfsdk/include/fpdfformfill.h
BUG=397834
Review URL: https://codereview.chromium.org/424883002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@286323 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are situations where the pdf plugin will initialize itself in such a way
that it never notifies content/renderer/ that it has started. In so doing, it
also fails to send a stop message, since it tries to ensure it doesn't send
mismatched start/stop messages.
Print preview decides when to display the preview based on when loading
stops. Since this only considers the page's content and not the pdf plugin's
initialization, there is a race condition where we may try to preview before
the plugin is ready. In this cases, we show "Loading preivew..." and never load
the actual preview.
There is a hack in place in print_preview_web_helper.cc to delay the process of
showing the preview to maximize the chance that the pdf plugin will be ready.
This change should allow us to rip that out.
BUG=376969
Review URL: https://codereview.chromium.org/397713005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283837 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=350782
Review URL: https://codereview.chromium.org/385173004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283481 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=389333
TEST=Manual, see bug.
Review URL: https://codereview.chromium.org/335993006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283268 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
outputs the width and height, in points, of a given PDF document page.
BUG=388517
Review URL: https://codereview.chromium.org/376083002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@282300 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This contains fixes for the following sorts of issues:
* Signedness mismatch
This relies on https://codereview.chromium.org/376003003 to make FPDF_FillRect()
take a 32-bit value for the color in order to make the changes here as simple
and clean as possible.
This also contains a few other cleanups to make code simpler or more consistent.
BUG=81439
TEST=none
Review URL: https://codereview.chromium.org/372273005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@282146 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
For cases such as Privet local printing when the pepper API is not initialized,
disable font mapping to prevent it from crashing.
BUG=391977
Review URL: https://codereview.chromium.org/378733002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@281653 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It appears we used to use a version script when compiling libpdf.so. This was
causing crashes such as the one in the associated bug. The reason given
for using the version map was to hide vendor symbols, but since the PDF code
is all open source now, this shouldn't be an issue.
BUG=386436
Review URL: https://codereview.chromium.org/351773005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@281157 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
TBR=brettw@chromium.org
Review URL: https://codereview.chromium.org/367893002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@281116 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: https://codereview.chromium.org/354513007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@280228 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This increases the performance of scrolling in OOP PDF by not sending viewport
changes via postMessage every time a scroll event occurs on the page. Instead,
scroll events are sent along with pepper DidChangeView messages, which is a
much more responsive way of updating the scroll position.
Unfortunately this introduces some issues coordinating zoom and scroll events
on the page. When a zoom happens in the container page, a scroll message
might be sent to the plugin via DidChangeView. Then we send a zoom change
message via postMessage. The result is that the zooming and scrolling
happen asynchronously and result in a flickering effect.
To avoid this, we first notify the plugin that we are about to zoom which
causes it to stop reacting to scroll messages. After we have finished zooming
we notify the plugin again so that it can continue reacting to scroll messages.
BUG=386920
Review URL: https://codereview.chromium.org/347763007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@279910 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
It was reported Adobe Reader rotates this way, and so does Mac's Preview.App.
BUG=369206
TEST=Manual, see bug.
Review URL: https://codereview.chromium.org/350803002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@279455 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This test was disabled because it was failing. A few changes have been made:
-The page zoom cannot be assumed to be 100% on load as it will depend on the screen size being tested on. So testPageSize now doesn't make that assumption.
-testAccessibilityWithPage was flaking because accessibility information was not always returned for the two text boxes. I spent a bit of time investigating, but couldn't work it out so I've left it partially disabled for now and filed crbug.com/378091.
-The files have all been moved to a more appropriate location (in particular the test was moved out of the data directory).
BUG=303491
Review URL: https://codereview.chromium.org/290803007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278340 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This test fails consistently on Linux Tests (dbg) (1)
[ RUN ] PDFExtensionTest.BasicPlugin
...
[1023:1023:0618/142028:INFO:CONSOLE(0)] "[SUCCESS] testPageSize", source: chrome-extension://mhjfbmdgcfjbbpaeojofohoefgiehjai/index.html?http://127.0.0.1:42118/pdf/test.pdf (0)
[17:17:0618/142028:WARNING:resource_message_handler.cc(49)] 'Post' message handler failed to complete successfully.
[17:17:0618/142028:ERROR:pepper_uma_host.cc(106)] Host or histogram name is not allowed to use the UMA API.
[17:17:0618/142028:WARNING:resource_message_handler.cc(49)] 'Post' message handler failed to complete successfully.
memory allocation bug: object at 0x7f5a852272c0 has never been allocated
BrowserTestBase signal handler received SIGTERM. Backtrace:
#0 0x7f9e4351c8b5 base::debug::StackTrace::StackTrace()
#1 0x00000462f8f2 content::(anonymous namespace)::DumpStackTraceSignalHandler()
#2 0x7f9e2fb2f4a0 \u003Cunknown>
#3 0x7f9e2fbe1a43 __poll
#4 0x7f9e30917ff6 \u003Cunknown>
#5 0x7f9e30918124 g_main_context_iteration
#6 0x7f9e434e49e5 base::MessagePumpGlib::Run()
<truncated, full output is in gzipped JSON output at end of step>
#31 0x7f9e34f05dc7 content::RunNamedProcessTypeMain()
#32 0x7f9e34f074df content::ContentMainRunnerImpl::Run()
#33 0x7f9e34f0528b content::ContentMain()
...
> Re-enable PDFExtensionTest.BasicPlugin
>
> This test was disabled because it was failing. A few changes have been made:
> -The page zoom cannot be assumed to be 100% on load as it will depend on the screen size being tested on. So testPageSize now doesn't make that assumption.
> -testAccessibilityWithPage was flaking because accessibility information was not always returned for the two text boxes. I spent a bit of time investigating, but couldn't work it out so I've left it partially disabled for now and filed crbug.com/378091.
> -The files have all been moved to a more appropriate location (in particular the test was moved out of the data directory).
>
> BUG=303491
>
> Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=273819
>
> Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=274186
>
> Review URL: https://codereview.chromium.org/290803007
TBR=raymes@chromium.org
Review URL: https://codereview.chromium.org/346693002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278191 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This test was disabled because it was failing. A few changes have been made:
-The page zoom cannot be assumed to be 100% on load as it will depend on the screen size being tested on. So testPageSize now doesn't make that assumption.
-testAccessibilityWithPage was flaking because accessibility information was not always returned for the two text boxes. I spent a bit of time investigating, but couldn't work it out so I've left it partially disabled for now and filed crbug.com/378091.
-The files have all been moved to a more appropriate location (in particular the test was moved out of the data directory).
BUG=303491
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=273819
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=274186
Review URL: https://codereview.chromium.org/290803007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278043 0039d316-1c4b-4281-b951-d872f2087c98
|