Closed Bug 906457 Opened 12 years ago Closed 12 years ago

Blank Editor with Mozilla Firefox 23 on XenForo Forums Running XenForo 1.1.5 or Below

Categories

(Core :: General, defect)

Product:
Core
Component:
General
Version:
2.0 Branch
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: amaury, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:23.0) Gecko/20100101 Firefox/23.0 (Beta/Release) Build ID: 20130814063812 Steps to reproduce: After Mozilla Firefox automatically updated itself for me yesterday morning from 22.0.0 to 23.0.1, I've been unable to edit my posts on XenForo forums running XenForo 1.1.5 or below. I've tried on KH-Vids (http://kh-vids.net/forum/) and DOTATalk (http://www.dotatalk.com/forum/), both running XenForo 1.1.4 and both containing the same issue. Additionally, I tried clearing my browser data last night before going to bed, and I'm still having the issue today. Actual results: Using KH-Vids for this example, I got a blank editor: http://i.imgur.com/rV0SQs3.png Expected results: Using XenForo Community, the official XenForo site, which is obviously running the latest version of XenForo 1.2.0, I should be seeing this on XenForo forums running XenForo 1.1.5 or below: http://i.imgur.com/H0n1UjP.png
I'd like to retract this, seeing as a fix for an old version of any software -- in this case, XenForo -- wouldn't be applied.
We would in fact fix things to not break old versions of web libraries, in general. Would you be willing to use http://mozilla.github.io/mozregression/ to try to narrow down when the problem appeared?
Flags: needinfo?(amaury)
I already said when it appeared? It showed up in Mozilla Firefox 23.0.1, the first 23 release. Or did you mean something else? =)
Flags: needinfo?(amaury)
The script I linked to would cut that down from "sometime in these 18 weeks" to "this particular day", which would make it a lot more likely that we can determine what caused the behavior change.
Flags: needinfo?(amaury)
It appeared on August 6, 2013, but was fine on August 5, 2013 and before.
Would you happen to have the http:// URIs from about:buildconfig for the relevant builds?
It's not really showing anything for me, so the dates are all I can provide. Seeing as it can be gotten around by going into the advanced editor, it's not a breaking bug by any means, so if it can't be fixed, it's not a big deal. However, here's a thread a user on XenForo Community created that may help: http://xenforo.com/community/threads/be-wary-of-firefox-23-0-xenforo-1-1-x.57692/
Flags: needinfo?(amaury)
about:buildconfig doesn't show anything for you?
It's not blank, but I don't see any http:// URLs. http://i.imgur.com/btIfcZh.png
Er, right, it's an https URL now.
I don't see any https stuff, either. I'm thinking the bug may be more on XenForo's side than Mozilla Firefox's. Not sure, though.
> I don't see any https stuff, either. It's right there in your screenshot, no? Under "Source" it says "Built from" and then a url. That's the url I'd like, for the two builds bracketing when the problem appeared.
This? http://hg.mozilla.org/releases/mozilla-release/rev/a55c55edf302 I'm sorry. I wasn't understanding you properly.
> This? http://hg.mozilla.org/releases/mozilla-release/rev/a55c55edf302 Yes, and the same for the other build in question.
You mean for Mozilla Firefox 22.0? If so, where do I find that? I'm only seeing 23.0 on the list.
We seem to be talking past each other... The bug appeared in a Firefox _release_ on Aug 6, because that's when we released Firefox 23. But it appeared in a Firefox _nightly_ sometime in the 18 weeks prior to that, during development of Firefox 23. The script I linked to in comment 2 would find the two _nightly_ builds before and after the problem appeared, and tell you what their "built from" identifiers were. If you want to find Firefox 22, it's at ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/ just like every single other Firefox release going back to 0.1 or so. But the basic problem I have here is that I have no steps to reproduce (without being able to try editing your posts or something), so I'm trying to figure out what might have caused the problem by asking the one person who can reproduce it (you) to figure out when it first appeared in a nightly build....
Sorry for not understanding. I'm really not trying to frustrate you or anything. Anyway, I'm not really not that great when it comes to things like that, so I created a test user here where you can try it yourself: http://www.dotatalk.com/forum/ Username: Bugzilla Password: testing Steps: 1. In the Off Topic forum, create a thread 2. After posting it, click Edit You'll see your text quickly flash and then go blank; the only way to edit is by clicking More Options and going into the advanced editor.
Amaury, thank you for the steps to reproduce and the login info. Looks like this problem was introduced between the April 9 and April 10 nightlies, by one of these checkins: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b1fb34b07c17&tochange=9db46ddfb517 Looking into what in there might have affected this.
OK, bisect shows: The first bad revision is: changeset: 128047:fc80e729a417 user: Boris Zbarsky <bzbarsky@mit.edu> date: Mon Apr 08 17:04:19 2013 -0400 summary: Bug 765780 part 1. Stop disallowing script and plug-ins in designMode documents. r=ehsan Looks like for some reason the forum is not initializing the TinyMCE editor after that change. What's odd is that other TinyMCE instances work fine.
Keywords: qawanted, testcase-wanted
FYI. The editor seems to work fine when middle click "Edit" link to open the editor in new tab
Reproducible on: - the latest FF 25 beta 2 (BuildID: 20130923194050): Mozilla/5.0 (Windows NT 6.1; rv:25.0) Gecko/20100101 Firefox/25.0 - Firefox 24.0 (BuildID: 20130910160258): Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Firefox/24.0 - the latest Nightly (BuildID: 20130924030202): Mozilla/5.0 (Windows NT 6.1; rv:27.0) Gecko/20100101 Firefox/27.0 Not reproducible on Chrome nor Opera. I confirm the same behavior as in comment 20: the editor works fine when I middle or right click the "Edit" link to open in New Tab, New Window or New Private Window. Also reproducible on Ubuntu 12.04 32bit with latest Nightly and Firefox 24.0.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: qawanted
OS: Windows 7 → All
QA Contact: alexandra.lucinet
The qawanted here is for figuring out what differs between this TinyMCE instance and every single other one we've tested with...
Keywords: qawanted
(In reply to Boris Zbarsky [:bz] from comment #22) > The qawanted here is for figuring out what differs between this TinyMCE > instance and every single other one we've tested with... I couldn't figure out the difference between those. Although, this is no longer an issue for me with both forums from description on Firefox 26 beta 6, Firefox 25 RC, latest Aurora nor Nightly on Windows 7 32bit, Mac OS X 10.9 and Ubuntu 13.04 32bit. I suspect this fix is due the update from Xenforo 1.1.4 to XenForo 1.2.2 since is no longer reproducible also with builds from comment 21. Could this be considered as a Tech Evangelism bug and closed?
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
(In reply to Alexandra Lucinet, QA Mentor [:adalucinet] from comment #23) > (In reply to Boris Zbarsky [:bz] from comment #22) > > The qawanted here is for figuring out what differs between this TinyMCE > > instance and every single other one we've tested with... > > I couldn't figure out the difference between those. > Although, this is no longer an issue for me with both forums from > description on Firefox 26 beta 6, Firefox 25 RC, latest Aurora nor Nightly > on Windows 7 32bit, Mac OS X 10.9 and Ubuntu 13.04 32bit. I suspect this fix > is due the update from Xenforo 1.1.4 to XenForo 1.2.2 since is no longer > reproducible also with builds from comment 21. > > Could this be considered as a Tech Evangelism bug and closed? It's not an issue in XenForo 1.2 because 1.2 introduced Redactor, a new editor. Also, I forgot to mention the issue was only when the rich text editor was enabled (where you can see the styling rather than just the BB code).
In other words, the issue is still there.
Issue is resolved - clearing old keywords - qa-wanted clean-up
Keywords: qawanted
You need to log in before you can comment on or make changes to this bug.