Bug 819183 (gfxglitch)

Rendering Issues after rotating Motorola Defy XT, Samsung Appeal, Galaxy Mini 2 (GT-S6500), Galaxy Ace Q (i827d), HP Touchpad, Galaxy Ace Plus

NEW
Assigned to

Status

()

Core
Graphics
P5
normal
5 years ago
3 years ago

People

(Reporter: Ryan, Assigned: gw280, NeedInfo)

Tracking

(Blocks: 1 bug)

Trunk
ARM
Android
Points:
---

Firefox Tracking Flags

(firefox17 affected, firefox18 affected, firefox19 affected, firefox20 affected, firefox21 affected, firefox22 affected, firefox23 affected, firefox24 affected, firefox25 affected, firefox26 affected, firefox27 affected, fennec+)

Details

(Whiteboard: gfx)

Attachments

(4 attachments)

(Reporter)

Description

5 years ago
Created attachment 689480 [details]
Buggy Rendering

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0
Build ID: 20121128060531

Steps to reproduce:

Open Firefox in Portrait

or

Open Firefox in Landscape


Actual results:

Web Page is rendered correctly on open. When you rotate the phone to landscape (when opened in portrait) or rotate the phone to portrait, the rendering gets "squished".




Expected results:

Webpage is rendered to fit landscape or portrait correctly.
How does http://nightly.mozilla.org Android build behave?
(Reporter)

Comment 2

5 years ago
The nightly still has the same type of behavior when switching between portrait/landscape.


Specs of my phone just in case:

DEFYXT557
Android 2.3.7
Kernel version: Apps_2.6.38.6-perf
Build Number: 1_65G_1027
OS: Windows 7 → Android
Hardware: x86_64 → ARM
Is the behaviour transient? i.e. if you try to pan or interact with the page, does it fix itself? How about rotating back, does that fix the problem? Or is just completely hosed once it gets into this state?
XT535

* Android 2.3
* 1GHz (MSM7227A) / 512MB 
* Adreno 200
Status: UNCONFIRMED → NEW
Ever confirmed: true
(Reporter)

Comment 5

5 years ago
If I rotate it back to the original orientation, the one when Firefox was opened, rendering goes back to normal. I can interact with the buggy state of the webpage, but it's only limited to scrolling, and it remains in the unusable buggy state like it does in the attachment.
I can't think of anything offhand that might cause this, particularly if it's happening on both release and nightly (i.e. it's not tiling-related). We would need to reproduce and investigate, but afaik we don't have any of these devices lying around.
Thanks, we've seen those before. This is caused by broken drivers that are out of date. Let me find the other bug report that was from another device.

Do you have an animated background?
I can't find the bug :(
(Reporter)

Comment 9

5 years ago
No animated wallpapers or backgrounds. I submitted a bug request with republic wireless but it's not going anywhere either. I cannot think I'd be the only one using this device trying Firefox for Android.

I did try restoring the device to factory settings as well but the bug remains.

Comment 10

5 years ago
I have this issue on my Defy XT as well.
I am rooted so if you need me to do anything special, let me know.
Can anything be done here?
tracking-fennec: --- → ?
status-firefox17: --- → affected
status-firefox18: --- → affected
status-firefox19: --- → affected
status-firefox20: --- → affected
BenWa, what can be done here?
Flags: needinfo?(bgirard)

Comment 13

5 years ago
If this is a driver issue... It might be fixed by the Over The Air update from Republic Wireless. I am guessing most of us are using Republic Wireless.
(In reply to Aaron Train [:aaronmt] from comment #4)
> XT535
> 
> * Android 2.3
> * 1GHz (MSM7227A) / 512MB 
> * Adreno 200

Aaron, does this mean you were able to reproduce? If so, can you show BenWa and Kats?
No was just listing the device spec from comment #0 and toggled to new as per the screenshot indication.
(In reply to Brad Lassey [:blassey] from comment #12)
> BenWa, what can be done here?

Since this is a driver bug the best we could do is spend time to try and work around the issue. It's hard to know how much time is required to come up with a work around for these kind of issues.

It may be possible to push a white/black frame ASAP to cover up the corruption.
Flags: needinfo?(bgirard)

Updated

5 years ago
Duplicate of this bug: 826356

Updated

5 years ago
Summary: Render Issue on Motorola Defy XT when switching between Portrait and Landscape → Rendering Issues on Motorola Defy XT

Comment 18

5 years ago
And are Defy XT users also experiencing the non landscape/portrait phenomenon that I show in my video in Bug 826356 where, while on a google search results page, if you put your cursor in the google search bar (not the firefox url bar), the keyboard appears and the top half of the page goes white, with a floating orange cursor and about 10 pixels of the page visible above the keyboard? : https://www.youtube.com/watch?v=BUYwKqPilSw&feature=player_detailpage#t=24s

Wondering if it's related and everyone's seeing it or it's just me.
related to bug 768882?
See Also: → bug 768882
(In reply to Aaron Train [:aaronmt] from comment #15)
> No was just listing the device spec from comment #0 and toggled to new as
> per the screenshot indication.

i was referring to moving it from unconfirmed to new
Chris can you take a look at Gene's phone?
Assignee: nobody → cpeterson
tracking-fennec: ? → +
After examining Gene's phone, I believe this is a tile rendering bug related to orientation changes.

When a page is loaded in portrait orientation and the user rotates the phone to landscape orientation, the page becomes scrambled. The page is rendered at half the landscape height and the horizontal tile stride looks incorrect. The attached Portrait_to_Landscape.png screenshot shows what looks like 9 portrait tiles rendered on side-by-side per landscape tile.

The layout engine knows the orientation's correct dimensions because focusing a text input field will display the orange text selection handle in the correct position. So this looks like a bug only in the graphics code's handling of orientation changes.
Summary: Rendering Issues on Motorola Defy XT → Tile rendering Issues when rotating Motorola Defy XT
Created attachment 700651 [details]
Gene's Portrait_to_Landscape.png
Created attachment 700652 [details]
Gene's Landscape_to_Portrait.png
Since this is a tile rendering bug, Cwiiis is probably a better person to fix the bug.
Assignee: cpeterson → chrislord.net
(In reply to Chris Peterson (:cpeterson) from comment #25)
> Since this is a tile rendering bug, Cwiiis is probably a better person to
> fix the bug.

I really don't think this has anything to do with tiles, tile-size doesn't change on orientation switch. Looks like a driver bug to me, as mentioned in previous comments - likely it isn't handling the surface resize correctly. Possibly something we can work around, but not having the device or any other device that exhibits this problem means there's nothing I can do about it.

What's the exact model number? I could expense it if I know exactly which model it is, though it's possible a phone I'd buy here wouldn't exhibit the bug due to updated firmware...

Comment 27

5 years ago
It happens on my phone which has these attributes :
Model : XT557
Android Version : 2.3.7
Baseband Version : PCR
Kernel Version : Apps_2.6.38.6-perf
Build Number : 1_65H_1027
Carrier : http://www.republicwireless.com/

If the problem isn't tile based, if someone in SF has the ability to diagnose it, they're welcome to use my phone all day any day.
Chris Lord does it make sense for you to expense it or maybe we could bring one to the mobile team week? I think this is a user report of the issue in the forums https://support.mozilla.org/en-US/questions/948702
Blocks: 801554
Another user report in the support forums using a Samsung Galaxy Appeal.
http://www.samsung.com/us/mobile/cell-phones/SGH-I827ZSAATT AT&T
Flags: needinfo?(chrislord.net)
Summary: Tile rendering Issues when rotating Motorola Defy XT → Tile rendering Issues when rotating Motorola Defy XT, Samsung Appeal

Updated

4 years ago
Duplicate of this bug: 841907
Galaxy Mini 2 Bug 841907. Re-requesting tracking for 21?
tracking-fennec: + → ?
Summary: Tile rendering Issues when rotating Motorola Defy XT, Samsung Appeal → Tile rendering Issues when rotating Motorola Defy XT, Samsung Appeal, Galaxy Mini 2 (GT-S6500)

Updated

4 years ago
status-firefox21: --- → affected
(In reply to Kevin Brosnan [:kbrosnan] from comment #28)
> Chris Lord does it make sense for you to expense it or maybe we could bring
> one to the mobile team week? I think this is a user report of the issue in
> the forums https://support.mozilla.org/en-US/questions/948702

Bringing one to the mobile work week would be handy, certainly. I'm going to rename this bug as it almost certainly has nothing to do with tiles.
Flags: needinfo?(chrislord.net)

Updated

4 years ago
Summary: Tile rendering Issues when rotating Motorola Defy XT, Samsung Appeal, Galaxy Mini 2 (GT-S6500) → Rendering Issues after rotating Motorola Defy XT, Samsung Appeal, Galaxy Mini 2 (GT-S6500)
tracking-fennec: ? → +

Updated

4 years ago
Duplicate of this bug: 845359

Comment 35

4 years ago
(In reply to Gene Wood [:gene] from comment #18)
> And are Defy XT users also experiencing the non landscape/portrait
> phenomenon that I show in my video in Bug 826356 where, while on a google
> search results page, if you put your cursor in the google search bar (not
> the firefox url bar), the keyboard appears and the top half of the page goes
> white, with a floating orange cursor and about 10 pixels of the page visible
> above the keyboard? :
> https://www.youtube.com/watch?v=BUYwKqPilSw&feature=player_detailpage#t=24s
> 
> Wondering if it's related and everyone's seeing it or it's just me.

Yes I see that phenomenon on my Galaxy Mini 2 (GT-S6500), along with the main phenomenon of this bug.

Comment 36

4 years ago
May or may not be relevant:

The scrambling phenomenon on my Galaxy Mini 2 (GT-S6500) seems to only occur when trying to change the orientation of WEBPAGES. It does not occur on the about:home page. I.e. if I am on the about:home page, then I can change orientation without getting scrambled.
See also the pictures appended to bug 845359.

Updated

4 years ago
status-firefox22: --- → affected
(Reporter)

Comment 37

4 years ago
(In reply to mirleau from comment #35)
> (In reply to Gene Wood [:gene] from comment #18)
> > And are Defy XT users also experiencing the non landscape/portrait
> > phenomenon that I show in my video in Bug 826356 where, while on a google
> > search results page, if you put your cursor in the google search bar (not
> > the firefox url bar), the keyboard appears and the top half of the page goes
> > white, with a floating orange cursor and about 10 pixels of the page visible
> > above the keyboard? :
> > https://www.youtube.com/watch?v=BUYwKqPilSw&feature=player_detailpage#t=24s
> > 
> > Wondering if it's related and everyone's seeing it or it's just me.
> 
> Yes I see that phenomenon on my Galaxy Mini 2 (GT-S6500), along with the
> main phenomenon of this bug.

Yes, I see this on the Defy XT.

Comment 38

4 years ago
I have the same issue on Defy XT557
Android 2.3.7
Kernel Apps_2.6.38.6-perf
So I have one of the affected phones at the moment and I'm looking at this - nothing obvious is failing, but it seems something with the surface negotiation process is going wrong and no error is being reported...

I'm going to try a few things, but atm I have nothing to say that sheds any further light on this situation :/
My best guess for this atm is that the drivers for this chipset don't support resizing EGL surfaces, and when we're told the surface has resized, actually, it hasn't - Perhaps destroying and recreating the surface on resize might fix this.

The device I'm testing with has an Adreno 200 chipset (note, not 205) - do all of these devices have that in common?

Comment 41

4 years ago
(In reply to Chris Lord [:cwiiis] from comment #40)
> My best guess for this atm is that the drivers for this chipset don't
> support resizing EGL surfaces, and when we're told the surface has resized,
> actually, it hasn't - Perhaps destroying and recreating the surface on
> resize might fix this.
> 
> The device I'm testing with has an Adreno 200 chipset (note, not 205) - do
> all of these devices have that in common?

Here is sysfs from bad case:

$ adb shell ls /sys/devices/platform
uevent
power
power.0
reg-dummy
footswitch-pcom.2
msm_dmov
msm_smd
msm_serial.0
msm_serial_hs.0
msm_serial_hsl.0
msm_serial.2
msm_nand
qup_i2c.0
qup_i2c.1
msm_otg
msm_hsusb
android_pmem.0
android_pmem.1
rndis
usb_diag
usb_fserial
android_pmem.2
msm_snd
msm_adspdec
msm_fb.0
lcdc_toshiba_fwvga_pt.0
msm_camera_s5k4e1.0
msm_camera_imx072.0
msm_camera_ov9726.0
mipi_renesas.0
kgsl-3d0.0
msm-dsp-audio.0
msm-codec-dai.0
msm-cpu-dai.0
mdp.0
mipi_dsi.1
wlan_ar6000_pm_dev
msm_sdcc.1
msm_sdcc.2
msm_hsusb_host.0
ram_console.0
alog_ram_console.0
msm-battery
w1-gpio
android_usb
usb_mass_storage
gpio-keys
bcm4330_bt_power
bluesleep
bcm4330_wifi_power
msm_camera_ov5640af.0
msm_camera_ov7692.0
msm-handset
local_loopback.100
DS.0
DIAG.0
RPCCALL.0
DATA1.0
DATA2.0
DATA3.0
DATA4.0
DATA5.0
DATA6.0
DATA7.0
DATA8.0
DAL00.0
DATA22.0
DATA5_CNTL.0
DATA6_CNTL.0
DATA7_CNTL.0
DATA8_CNTL.0
oncrpc_router
rs30000081.65536
rs30000061.393216
rs30000060.458752
rs30000003.-21185617
rs30000002.196608
rs30000000.-1666429071
rs3000fffd.0
rs3000001d.-1165732093
rs3000005b.-1509783888
rs3000003c.851968
rs3000001b.262144
rs3000001a.262144
rs30000019.196608
rs30000017.65536
rs30000016.196608
rs30000091.196608
rs30000071.65536
rs30000014.131072
rs30000013.196608
rs30000012.262144
rs3000fe00.-1473427932
rs3000008c.327680
rs30000010.65536
rs3000006b.65536
rs3000000e.589824
rs30000089.327680
rs30000069.-84731838
rs300000a5.131072
rs30000048.262144
rs3000000a.65536
adsp_AUDPLAY0TASK
adsp_AUDPLAY1TASK
adsp_AUDPLAY2TASK
adsp_AUDPLAY3TASK
adsp_AUDPPTASK
adsp_AUDPREPROCTASK
adsp_RMTASK
adsp_AUDRECTASK
adsp_VFETASK
adsp_QCAMTASK
adsp_LPMTASK
adsp_JPEGTASK
adsp_VIDEOTASK
adsp_VDEC_LP_MODE
adsp_VIDEOENCTASK
adsp_VIDEO_AAC_VOC_TURBO
adsp_VIDEO_AMR_TURBO
adsp_WM_TURBO_MODE
adsp_VDEC_LP_MODE_TURBO
adsp_AUDREC1TASK
rs300000a3.131072
rs30000064.65536
headset_sensor.0
alarm
light.0
orientation.0
proximity.0
mipi_toshiba_fwvga.769
mipi_dsi.590593
mdp.590593
msm_fb.590593
soc-audio

$ adb shell cat /proc/cpuinfo
Processor       : ARMv7 Processor rev 1 (v7l)
BogoMIPS        : 503.70
Features        : swp half thumb fastmult vfp edsp thumbee neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xc05
CPU revision    : 1

Hardware        : QCT MSM7x27a FFA
Revision        : 0000
Serial          : 0000000000000000
Duplicate of this bug: 847431
What I've looked at/tried:

- Looked at event ordering (is fine)
- Tried doing the resize in one shot instead of the current two-step process (still fails)
- Tried destroying the surface and recreating it on every change (just doesn't work, and can put the phone in an odd state - I might have got this wrong somehow, or broken some assumptions made in native gfx)
- Tried querying the surface width/height after creation, in case they differ to what we've been told by the changed event (they don't)

It just seems that the surface resizing on this device is broken. I would expect that if we tore down the LayerSurfaceView and recreated it on surface change, this would probably fix the issue, but also likely cause ugly artifacts (though that's obviously preferable to the current behaviour).

Will try a couple more things, but I'm kinda stumped on this and I think it'll take more considerable time to figure this out properly - I think it might be better for someone in gfx with some decent gpu debugging experience to take a look (Jeff maybe?)
Ok, I've found a 'fix' for this - If I set visibility to invisible, then visible on the layout change of the SurfaceView, it works as expected. This looks fine too, though I don't know if this affects how it looks on devices that don't suffer from this problem (will test next)
On an unaffected device, the fix causes intermittent flickering on rotate. It'd be good if we could find a better way of doing whatever the fix actually causes to happen, and failing that, to only use it based on chipset and/or driver version.

For reference, this is the output for an affected driver:

E/GeckoConsole(12825): Version: OpenGL ES 2.0 1849878
E/GeckoConsole(12825): Vendor: Qualcomm
E/GeckoConsole(12825): Renderer: Adreno (TM) 200
E/GeckoConsole(12825): FBO Texture Target: TEXTURE_2D
Created attachment 720740 [details] [diff] [review]
Work-around for buggy surface resizing

Comment 47

4 years ago
(In reply to Chris Lord [:cwiiis] from comment #40)

> 
> The device I'm testing with has an Adreno 200 chipset (note, not 205) - do
> all of these devices have that in common?

Hi Chris, I own the Galaxy Mini 2 (GT-S6500). I'm not sure how to determine the chipset you're asking for, but here's the output of the statements that Dmitri Khokhlov ran:

/ # ls /sys/devices/platform
DAL00.0                   i2c-gpio.5                rs30000002.196608
DATA1.0                   i2c-gpio.6                rs30000003.-21185617
DATA11.0                  kgsl-3d0.0                rs3000000a.65536
DATA2.0                   lcdc.0                    rs3000000e.589824
DATA3.0                   lcdc.196609               rs30000010.65536
DATA4.0                   lcdc_trebon_hvga.0        rs30000012.262144
DS.0                      lcdc_trebon_hvga.1        rs30000013.196608
RPCCALL.0                 leds-msm-pdm.0            rs30000014.131072
adsp_AUDPLAY0TASK         local_loopback.100        rs30000016.196608
adsp_AUDPLAY1TASK         mdp.0                     rs30000019.196608
adsp_AUDPLAY2TASK         mdp.196609                rs3000001a.262144
adsp_AUDPLAY3TASK         msm-battery               rs3000001b.262144
adsp_AUDPPTASK            msm-codec-dai.0           rs3000001d.-1165732093
adsp_AUDPREPROCTASK       msm-cpu-dai.0             rs3000003c.851968
adsp_AUDREC1TASK          msm-dsp-audio.0           rs30000048.262144
adsp_AUDRECTASK           msm-handset               rs3000005b.-1509783888
adsp_JPEGTASK             msm_adspdec               rs3000005f.262144
adsp_LPMTASK              msm_camera_sr300pc20.0    rs30000060.458752
adsp_QCAMTASK             msm_dmov                  rs30000061.393216
adsp_RMTASK               msm_fb.0                  rs30000064.65536
adsp_VDEC_LP_MODE         msm_fb.196609             rs30000069.-84731838
adsp_VDEC_LP_MODE_TURBO   msm_hsusb                 rs3000006b.65536
adsp_VFETASK              msm_nand                  rs30000071.65536
adsp_VIDEOENCTASK         msm_otg                   rs30000081.65536
adsp_VIDEOTASK            msm_sdcc.1                rs30000089.327680
adsp_VIDEO_AAC_VOC_TURBO  msm_sdcc.2                rs3000008c.327680
adsp_VIDEO_AMR_TURBO      msm_sdcc.3                rs30000091.196608
adsp_WM_TURBO_MODE        msm_serial.0              rs300000a3.131072
alarm                     msm_serial_hs.0           rs300000a5.131072
alps                      msm_smd                   rs300000a7.65536
android_pmem.0            msm_snd                   rs3000fe00.-1473427932
android_pmem.1            msm_vibrator              rs3000fffd.0
android_pmem.2            oncrpc_router             sec_jack
android_usb               pmic-leds                 soc-audio
bt_power.0                power                     uevent
dpram                     power.0                   usb_diag
footswitch-pcom.2         qup_i2c.0                 usb_fserial
gpio-event                qup_i2c.1                 usb_mass_storage
i2c-gpio.2                reg-dummy                 wlan_ar6000_pm_dev
i2c-gpio.3                rndis
i2c-gpio.4                rs30000000.-605429855


/ # cat /proc/cpuinfo
Processor       : ARMv7 Processor rev 1 (v7l)
BogoMIPS        : 122.47
Features        : swp half thumb fastmult vfp edsp thumbee neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xc05
CPU revision    : 1

Hardware        : QCT MSM7x27a FFA
Revision        : 0000
Serial          : 0000000000000000

Comment 48

4 years ago
(In reply to Chris Lord [:cwiiis] from comment #40)
> 
> The device I'm testing with has an Adreno 200 chipset (note, not 205) - do
> all of these devices have that in common?

Or else maybe this spec helps:
http://www.gsmarena.com/samsung_galaxy_mini_2_s6500-3883.php
(In reply to mirleau from comment #47)
> (In reply to Chris Lord [:cwiiis] from comment #40)
> Hi Chris, I own the Galaxy Mini 2 (GT-S6500). I'm not sure how to determine
> the chipset you're asking for, but here's the output of the statements that
> Dmitri Khokhlov ran:

You needn't worry, this is the device I tested on :)

The most useful output I think will be the GL driver vendor string - this gets output on the log on startup, you should see some lines similar to what I posted in comment #45.

Comment 50

4 years ago
is this fix pushed to beta?
can we get apk for testing?

Updated

4 years ago
Duplicate of this bug: 848259
(In reply to Dmitri Khokhlov from comment #50)
> is this fix pushed to beta?
> can we get apk for testing?

No.
Alias: gfxglitch
Summary: Rendering Issues after rotating Motorola Defy XT, Samsung Appeal, Galaxy Mini 2 (GT-S6500) → Rendering Issues after rotating Motorola Defy XT, Samsung Appeal, Galaxy Mini 2 (GT-S6500), Galaxy Ace Q (i827d)
Whiteboard: gfx
(In reply to Aaron Train [:aaronmt] from comment #52)
> (In reply to Dmitri Khokhlov from comment #50)
> > is this fix pushed to beta?
> > can we get apk for testing?
> 
> No.

To elaborate, the fix attached to this bug interferes with phones that aren't affected by this bug (it causes flickering on rotate). We still need to investigate to figure out what exactly this patch is doing at a lower level to see if we can do that in a way that doesn't cause flickering.
(In reply to Chris Lord [:cwiiis] from comment #46)
> Created attachment 720740 [details] [diff] [review]
> Work-around for buggy surface resizing

Can we land this behind a default-disabled pref? That way at least we have some sort of fix for people who run into this problem.
Duplicate of this bug: 845360
Ping re: ^?

Updated

4 years ago
Duplicate of this bug: 768882

Updated

4 years ago
Summary: Rendering Issues after rotating Motorola Defy XT, Samsung Appeal, Galaxy Mini 2 (GT-S6500), Galaxy Ace Q (i827d) → Rendering Issues after rotating Motorola Defy XT, Samsung Appeal, Galaxy Mini 2 (GT-S6500), Galaxy Ace Q (i827d), HP Touchpad
(In reply to Dmitri Khokhlov from comment #50)
> can we get apk for testing?

http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/kgupta@mozilla.com-398c04f28527/try-android/fennec-22.0a1.en-US.android-arm.apk
Btw I handed off the Galaxy Mini 2 that reproduces this problem to BenWa, who said he would take a look at it at some point.
I just want to report that the problem is verified fixed for our forum user who had the problem with a Samsung Galaxy mini2 GT-S6500.
I forgot: he installed the apk given by Aaron in comment 58.

Comment 62

4 years ago
I just installed the APK on my Samsung Galaxy mini2 GT-S6500. The issue seems to be fixed for me.
(In reply to Kartikaya Gupta (email:kats@mozilla.com) from comment #54)
> (In reply to Chris Lord [:cwiiis] from comment #46)
> > Created attachment 720740 [details] [diff] [review]
> > Work-around for buggy surface resizing
> 
> Can we land this behind a default-disabled pref? That way at least we have
> some sort of fix for people who run into this problem.

Chris, re ^?
Flags: needinfo?(chrislord.net)
(In reply to Aaron Train [:aaronmt] from comment #63)
> (In reply to Kartikaya Gupta (email:kats@mozilla.com) from comment #54)
> > (In reply to Chris Lord [:cwiiis] from comment #46)
> > > Created attachment 720740 [details] [diff] [review]
> > > Work-around for buggy surface resizing
> > 
> > Can we land this behind a default-disabled pref? That way at least we have
> > some sort of fix for people who run into this problem.
> 
> Chris, re ^?

I guess we could, but I'd really rather someone from gfx team looked at this before resorting to that. It's an ugly 'fix' that may well have a much better and widely applicable equivalent.
Flags: needinfo?(chrislord.net)

Updated

4 years ago
status-firefox23: --- → affected
Component: Graphics, Panning and Zooming → Graphics
Product: Firefox for Android → Core
Version: Firefox 17 → Trunk
Assigning this to Milan to find a suitable taker in the gfx team - I think we really ought to take a better look at this before committing my awful, awful 'fix' :)

Note, I'll be on PTO for 2 weeks after today, but I'll try to reply to needinfo's.
Assignee: chrislord.net → milan

Updated

4 years ago
Duplicate of this bug: 911598

Updated

4 years ago
status-firefox24: --- → affected
status-firefox25: --- → affected
status-firefox26: --- → affected
Summary: Rendering Issues after rotating Motorola Defy XT, Samsung Appeal, Galaxy Mini 2 (GT-S6500), Galaxy Ace Q (i827d), HP Touchpad → Rendering Issues after rotating Motorola Defy XT, Samsung Appeal, Galaxy Mini 2 (GT-S6500), Galaxy Ace Q (i827d), HP Touchpad, Galaxy Ace Plus
Any update here?

Comment 68

4 years ago
Can we have the "awful fix" waiting for a better one, or at least an updated apk (i have stability issues with the actual published in #58).
The awful fix would be a severe performance impact for every other user of Firefox for Android.

Comment 70

4 years ago
It has been mentionned that it could be a default-disabled about:config option.

Updated

4 years ago
status-firefox27: --- → affected
Not sure we can review the java code, but, George, can you get the device from BenWa and see if he remembers the details and see if there is something we can do on our side instead of Chris' "bad" fix?
Assignee: milan → gwright
Flags: needinfo?(gwright)
filter on [mass-p5]
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.