Commit Graph

19 Commits

Author SHA1 Message Date
Joel Maher
f27ae228e6 Bug 760264 - when running reftests on android native, we have a failure in layout/reftests/text-overflow/scroll-rounding.html. r=ajuma 2012-06-13 14:20:45 -04:00
Joel Maher
d63c5a0460 Bug 748088 - Native android reftest are not testing OMTC+OGL. r=ajuma 2012-06-01 08:42:38 -04:00
Phil Ringnalda
df7a7d5e53 Bug 668849 - give up on testing spellcheck with text-overflow on WinXP 2012-05-28 19:37:14 -07:00
Robert O'Callahan
d5ca0ea99a Bug 735898. Mark test as passing on Android 2012-04-13 23:50:15 +12:00
Robert O'Callahan
d0dd680745 Bug 733607. Restructure logic to compute snapped bounds of display items in layer coordinates. Moves responsibility for computing snapped bounds from within the display items to callers of GetBounds/GetOpaqueRegion. r=tnikkel
Previously we snapped the results of nsDisplayItem::GetBounds and
nsDisplayItem::GetOpaqueRegion internally. By tracking which display items were
inside transforms, we disabled snapping quite conservatively whenever an ancestor
had a transform, which is undesirable.

With this patch, we don't snap inside GetBounds or GetOpaqueRegion, but just return
a boolean flag indicating whether the item will draw with snapping or not. This flag
is conservative so that "true" means we will snap (if the graphics context has a transform
that allows snapping), but "false" means we might or might not snap (so it's always safe
to return false).

FrameLayerBuilder takes over responsibility for snapping item bounds. When it converts
display item bounds to layer pixel coordinates, it checks the snap flag returned from
the display item and checks whether the transform when we draw into the layer will be
a known scale (the ContainerParameters scale factors) plus integer translation. If both
are true, we snap the item bounds when converting to layer pixel coordinates. With
this approach, we can snap item bounds even when the items have ancestors with active
transforms.
2012-04-10 23:24:18 +12:00
Mats Palmgren
c7e06fddef Bug 672944 - Test -moz-box text-overflow. r=roc 2012-01-28 04:35:59 +01:00
Mats Palmgren
5c9659eaaf Bug 690187 - Clip or suppress a marker if it makes the line empty. r=roc 2011-12-19 15:48:31 +01:00
Mats Palmgren
9b7d613762 Bug 684266 - Do ellipsing on the end-edge only when a single value was specified for text-overflow. r=bzbarsky r=roc 2011-10-12 18:20:46 +02:00
Benoit Girard
95f511b8f5 Bug 676831 - Mark Android OpenGL Reftest failures for regression testing. r=joe
--HG--
extra : rebase_source : b5458fa13fc6277560eb0ebc3e4e31f6c04b4e6c
2011-09-19 13:05:15 -07:00
Mats Palmgren
e932421b76 Bug 677582 - Tests for CSS3 text-overflow: <left> <right>. r=roc 2011-08-20 22:41:39 +02:00
Mats Palmgren
0cfc6eb31b Test text-overflow:ellipsis on table-cell. b=nobug r=test-only 2011-07-26 19:22:47 +02:00
Mats Palmgren
09f019d5d9 Bug 669284 - reftest. 2011-07-06 12:03:23 +02:00
Mats Palmgren
6944b15b92 Disable newly added reftest for bug 667010 on Android to fix orange. r=test-only 2011-07-04 10:21:50 +02:00
Mats Palmgren
cff2b748ef Bug 668919 - The ellipsis with text-overflow: ellipsis is sometimes one pixel too low. r=roc 2011-07-04 07:47:59 +02:00
Mats Palmgren
1a4bff05e9 Bug 667010 - "ASSERTION: unexpected block frame" with text-overflow: ellipsis, <fieldset>. r=roc 2011-07-04 07:47:59 +02:00
Michael Ventnor
a25f3afc78 New, better reftest for bug 666689 r=roc 2011-07-04 14:59:19 +10:00
Michael Ventnor
5b88cf2c15 Implement text-shadow for the text-overflow marker text (ellipsis) r=roc 2011-07-01 16:43:11 +10:00
Mats Palmgren
ea62e4dc99 Bug 666669 - Test rendering of selected text, background and selection decorations with text-overflow. r=roc 2011-06-30 02:56:49 +02:00
Mats Palmgren
fb9132ab57 Bug 312156 - Tests for CSS3 text-overflow. r=roc 2011-06-22 20:11:48 +02:00