Closed Bug 523929 Opened 16 years ago Closed 16 years ago

Typing in chat box not working

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED WORKSFORME

People

(Reporter: ria.klaassen, Assigned: dmandelin)

References

(
URL
)

Details

(Keywords: regression, Whiteboard: [3.6b1][works now?])

A MozillaZine forum user reports that omegle.com chat is not working. I tested this and was able to reproduce. But there is no problem if JIT is enabled. The first build of September 2009 still worked fine so it must be a fairly new bug.
Link to SurlyDuff's post: http://forums.mozillazine.org/viewtopic.php?p=7805025#p7805025
OS: Windows XP → Windows Vista
(In reply to comment #0) > But there is no problem if JIT is enabled. Error, must be: there is no problem if JIT is disabled.
OS: Windows Vista → Windows XP
Thanks Ria for initiating this. The absence or presence of the text area doesn't seem to depend on jit state. In my scenario, using NoScript extension, the difference is whether or not Omegle.com is enabled (allowed) or disabled (blocked). That is, with the site blocked the text area is available but with the site allowed the text area does not even appear. Does this suggest a problem with scripts?
i confirm this on windows 7 also. with jit.chrome off, the textbox is disabled. build Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2b1) Gecko/20091022 Firefox/3.6b1
Flags: blocking1.9.2?
actually its disabled if jit.chrome OR jit.content is disabled. if any one of the two are enabled, the textbox breaks.
Can we get a local copy attached, so we can start reducing (or finding a regression range more effectively)? Thanks, guys!
Flags: blocking1.9.2? → blocking1.9.2+
I'm also finding this in Seamonkey Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.5pre) Gecko/20091021 SeaMonkey/2.0.1pre ID:20091021002920
Whiteboard: [3.6b1]
Yep, that sure is a tracemonkey merge. Hmph. Up for bisecting the tracemonkey nightlies?
As given by Tony on IRC this is all/all. I will run a hg bisect once I wake up tomorrow morning.
Keywords: regressionwindow-wanted
OS: Windows XP → All
Hardware: x86 → All
This bug has been regressed by the fix on bug 504797: Crash on Google Docs with jit enabled.
Blocks: 504797
Keywords: regressionwindow-wanted
Assignee: general → dmandelin
What are the STR, and exactly what is the failure symptom? I just tried to reproduce this with a nightly but I didn't find a problem. I loaded omegle.com, and I expected the text box to type chats in to be disabled or invisible, but it was there and I could type in it. I tried setting javascript.options.jit.chrome to false, and it still worked. I tried setting javascript.options.jit.(chrome|content) both to false and the text box also worked that way.
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.3a1pre) Gecko/20091109 Minefield/3.7a1pre Thanks for testing. Yes, it is fixed now. Until someone finds out by what patch, resolving WFM.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Problem has been seen again in FF3.6b2 and b3 Omegle chat won't enable the textbox, both JIT is set to true. I'm not sure what could be wrong with it. Further testing jit.chrome | true jit.content | false works.
ACK. It's not fixed. Tested with Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2b4pre) Gecko/20091118 Namoroka/3.6b4pre ID:20091118034701
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Is this related to bug 524826? A fix for that just went into tracemonkey branch. It's not in m-c yet but will be soon I imagine.
Correction, fix went into m-c today.
(In reply to comment #17) > Is this related to bug 524826? A fix for that just went into tracemonkey > branch. It's not in m-c yet but will be soon I imagine. I cannot bet. This particular problem is 1.9.2 branch only. Trunk isn't affected. I have started a try server build with Brendan's patch but I don't know if that will succeed. I will report back.
Status: REOPENED → NEW
Build failed because the patch cannot be applied. Looks like other fixes are necessary. Given that I will not be able to test it on 1.9.2. http://tinderbox.mozilla.org/showlog.cgi?log=MozillaTry/1258628132.1258628454.14533.gz
Is there a way to test this other than jumping on Omegle and trying it out? I feel funny about jumping into chat rooms to test and leaving after 3 seconds.
You don't have to worry. Looks like it's a 1:1 channel with a bot? in the first place. They would have killed me already. :)
Don't worry, at best it will be a random guy who wants to flirt with you.
Thanks for the moral support. :-) I just tested and found: mozilla-1.9.2 nightly build of 11/18: busted mozilla-1.9.2 nightly build of 11/19: works I looked at the pushlog and there aren't many changesets that were pushed that day, but none of them jumped out at me as being particularly likely to be the fix.
Whiteboard: [3.6b1] → [3.6b1][works now?]
Changesets: http://hg.mozilla.org/releases/mozilla-1.9.2/pushloghtml?fromchange=b4c505cfcdbd&tochange=a2af57fed584 A couple of JavaScript Engine patches have been checked-in yesterday. Could one of those have fixed that problem? It's working for me too with todays Namoroka build.
(In reply to comment #25) > Changesets: > http://hg.mozilla.org/releases/mozilla-1.9.2/pushloghtml?fromchange=b4c505cfcdbd&tochange=a2af57fed584 > > A couple of JavaScript Engine patches have been checked-in yesterday. Could one > of those have fixed that problem? It's working for me too with todays Namoroka > build. I looked through that list and did not see anything particularly likely. I figured there are better things to do than track down the exact rev that fixed it, since it is fixed everywhere. If not, let me know and I will bisect the changesets. In the meantime, I'm gonna mark it fixed again.
Status: NEW → RESOLVED
Closed: 16 years ago → 16 years ago
status1.9.2: --- → final-fixed
Resolution: --- → FIXED
Don't know exactly what fixed -> WORKSFORME.
Resolution: FIXED → WORKSFORME
Problem RESOLVED in the Namoroka Build. No idea what fixed it also. But hey it works. On that note, I noticed facebook chat seems to be displayed wrong. Should I report the bug ?
(In reply to comment #28) > On that note, I noticed facebook chat seems to be displayed wrong. Should I > report the bug ? If it's the same when running Firefox in Safe Mode then yes. But please scan through https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced;short_desc=facebook%20chat;short_desc_type=allwordssubstr It looks like there are some reports too. I will check those.
Verified with Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2b4pre) Gecko/20091119 Namoroka/3.6b4pre ID:20091119033555
Status: RESOLVED → VERIFIED
status1.9.2: final-fixed → ---
You need to log in before you can comment on or make changes to this bug.