Last modified: 2012-12-07 18:11:13 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T44763, the corresponding Phabricator task for complete and up-to-date bug report information.

Bug 42763 - [reply] doesn't work: wrapReplyText is not defined


Summary:	[reply] doesn't work: wrapReplyText is not defined

Status:	RESOLVED WORKSFORME

Product:	Wikimedia
Classification:	Unclassified
Component:	Bugzilla (Other open bugs)
Version:	unspecified
Hardware:	All All

Importance:	Normal minor (vote)
Target Milestone:	---
Assigned To:	Andre Klapper

URL:
Whiteboard:
Keywords:	code-update-regression

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2012-12-06 04:23 UTC by Liangent
Modified:	2012-12-07 18:11 UTC (History)
CC List:	3 users (show)

See Also:
Web browser:	---
Mobile Platform:	---
Assignee Huggle Beta Tester:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Liangent 2012-12-06 04:23:08 UTC

In Firefox (Iceweasel) 17.0:

Error: ReferenceError: wrapReplyText is not defined
Source File: https://bugzilla.wikimedia.org/show_bug.cgi?id=42351
Line: 213

Comment 1 Andre Klapper 2012-12-06 12:12:57 UTC

Thanks. Seen this once mentioned on IRC too, so I can now believe that this wasn't a One-off error.

Comment 2 Andre Klapper 2012-12-06 12:58:32 UTC

Function is only called in template/en/default/bug/edit.html.tmpl, and we do NOT have a custom code version of that file. And I cannot reproduce the problem. Grr.

Comment 3 Liangent 2012-12-06 13:45:06 UTC

(In reply to comment #1)
> Thanks. Seen this once mentioned on IRC too, so I can now believe that this
> wasn't a One-off error.

It works for me now this time...

Comment 4 Andre Klapper 2012-12-06 15:34:00 UTC

Liangent: Can you rule out that these are cache issues?

<^demon> I've had a couple of transient JS errors since the BZ upgrade when the old JS was stuck in my cache.
<^demon> (Like that dupe searching thing)
<^demon> Jarry1250: Have you tried a hard refresh?
<Jarry1250> Yup, was trying that as you wrote.
<Jarry1250> Did fix it.

Comment 5 Liangent 2012-12-06 15:38:15 UTC

(In reply to comment #4)
> Liangent: Can you rule out that these are cache issues?

I'm trying it again and it works, and I imagine they're cache issues.

Wikimedia Bugzilla is closed!

Search

Personal tools

Navigation

Links