Closed Bug 827144 Opened 12 years ago Closed 12 years ago

Followup on bug 811509 - twitter everything.me app does not repaint login text field

Categories

(Firefox OS Graveyard :: General, defect)

Product:
Firefox OS Graveyard
Component:
General
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(blocking-b2g:-, blocking-basecamp:-)

Status:
RESOLVED WORKSFORME
Project Flags:
blocking-b2g -
blocking-basecamp -

People

(Reporter: jsmith, Assigned: jrmuizel)

References

Details

(Whiteboard: [triage:1/16])

Build: 1/6/2013 Device: Unagi Steps: 1. Launch the twitter everything.me app 2. Select sign in 3. Start typing in the username field Expected: The user should be able to see the text that's being typed. Actual: No text renders on the text field. Also confirmed this at the hotel's IBahn site. So I'm not sure bug 811509 was fixed correctly.
Blocks: 811509
blocking-basecamp: --- → ?
Can you reproduce this on any non-qualcomm hardware. I think this may be a driver bug?
(In reply to Jeff Muizelaar [:jrmuizel] from comment #1) > Can you reproduce this on any non-qualcomm hardware. I think this may be a > driver bug? What hardware specifically would I have to use to test this out that is not qualcomm hardware? I only have an Unagi device and an Otoro device.
blocking-basecamp: ? → ---
(In reply to Jason Smith [:jsmith] from comment #2) > (In reply to Jeff Muizelaar [:jrmuizel] from comment #1) > > Can you reproduce this on any non-qualcomm hardware. I think this may be a > > driver bug? > > What hardware specifically would I have to use to test this out that is not > qualcomm hardware? I only have an Unagi device and an Otoro device. A Galaxy SII or Pandaboard. I have an SII that can check tomorrow.
This is a followup to a blocker, does it need to block?
blocking-basecamp: --- → ?
Assignee: nobody → jmuizelaar
(In reply to Milan Sreckovic [:milan] from comment #4) > This is a followup to a blocker, does it need to block? Don't know. Jeff's comment implies this could be a driver issue. We should confirm that it is a driver issue though.
Depends on: 826378
Jeff, please let us know once you've determined if this is a driver issue or not.
Flags: needinfo?(jmuizelaar)
Need to clarify whether this is a driver issue before we can determine blocking status.
Flags: needinfo?
Michael, any way to figure out whether this is a driver issue?
Flags: needinfo? → needinfo?(mvines)
Move to tef+ per mvines
blocking-b2g: --- → tef+
blocking-basecamp: ? → -
Vlad's new layers tool (bug 830881) could be used to see what size layer we're trying to composite.
Whiteboard: [triage:1/16]
I can't reproduce this in a build from $ (cd gecko/ && git rev-parse HEAD && cd ../gaia && git rev-parse HEAD) 2751cf873c70a03933c407d3bc06003e72c7fbc3 3c84fa2b74b3dbe591f0d4fbedbac9aac5ca4654 Please re-nom if anyone still can.
blocking-b2g: tef+ → -
Flags: needinfo?(mvines)
Flags: needinfo?(jmuizelaar)
Keywords: qawanted
QA Contact: jsmith
Yeah, I can't reproduce this anymore either. It looks like twitter changed.
Sounds like we should close this.
Status: NEW → RESOLVED
Closed: 12 years ago
Keywords: qawanted
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.