15838 - Animated gifs as text widget backgrounds cause the app to be unusable

Status: RESOLVED FIXED

(Core :: Layout: Form Controls, enhancement, P4)

Description

[Stuart Parmenter]

Placing an animated gif as the background of a text widget (i.e. the URL bar)
causes the UI to be completely unresponsive.

Comment 1

[buster]

pav:  is this really dogfood?  Are there important pages/XUL out there that
actually do this, that will keep people from using the app?  Convince me this is
a high priority bug and I'll go after it, otherwise it'll wait until after beta.

Comment 2

[Stuart Parmenter]

no.  its not important (for beta) :-)  feel free to push it off.

Comment 3

[leger]

Sorry...putting on PDT- radar

Comment 4

[Kathleen :Brade]

setting to M20 for triage post-beta

Comment 5

[gerardok]

QA Contact update.

Comment 6

[leger]

Putting dogfood in the keyword field.

Comment 7

[Simon Fraser [no longer active]]

This sounds like perf, I'll take it. I see no reason why it's dogfood, tho.

Comment 8

[Stuart Parmenter]

its not.

Comment 9

[ekrock's old account (dead)]

Moving to FUTURE and marking relnote. I'm comfortable with making the use of 
animated GIFs as a text widget background unsupported for FCS. (In fact, editing 
text over an animated GIF sounds like a very unpleasant UE, so I'm not sure 
you'd want to inflict this on the user for ordinary content/business usage. It 
might be cool for very hip experimental browsers, but we can live without this 
for FCS.)

Comment 10

[rubydoo123]

assigning this to Kevin -- this is really a view manager issue

Comment 11

[Kevin McCluskey (gone)]

This bug has been marked "future" because the original netscape engineer working 
on this is over-burdened. If you feel this is an error, that you or another 
known resource will be working on this bug,or if it blocks your work in some way 
-- please attach your concern to the bug for reconsideration. 

Comment 12

[bsharma]

Updating QA contact.

Comment 13

[Gervase Markham [:gerv]]

It seems unclear to me whether this bug requires either of a "developer" or 
"user" release note. If anyone feels it does, can they please draft one and then 
nominate with the relnote-user or relnote-rtm strings in the Status Whiteboard.

Thanks :-)

Gerv

Comment 14

[Vladimir Ermakov]

QA Contact Update

Comment 15

[basic]

is this still an issue?

Comment 16

[Kevin McCluskey (gone)]

Build moving all existing future-P3 bugs to future-P4.

Comment 17

[José Jeria]

This bugs seems to be outdated, is this still an issue? If yes, a testcase or an
url would be good.