Page MenuHomePhabricator

FormEdit - JS Error in combination with skin vector and wikieditor
Closed, ResolvedPublic

Description

Author: korinek

Description:
error

I got a Browser Error Message if I combine formedit, vector skin, wikieditor on freetext field and work with internet explorer. Firefox didn't show the error.

This error has been reproduced on a new wiki install as well.
In my tests the first appearance seems to be in SemanticBundle-20130226.tgz.
SemanticBundle-20130929.tgz was OK.

Client facts:
Windows 7 64bit
IE 10.0.9200.16521

Cleanwiki install facts:
MediaWiki 1.21.2
PHP 5.3.3-7+squeeze14 (apache2handler)
MySQL 5.0.51a-24+lenny5

Download:
SemanticBundle-20130929.tgz

Installed extensions

Semantic extensions
Semantic Bundle (Version 1.8.0.4)
Semantic Forms (Version 2.5.2)
Semantic MediaWiki (Version 1.8.0.4)

Parser hooks
SyntaxHighlight (Version 1.0.8.11)

Other
Validator (Version 0.5.1)
Vector (Version 0.3.0)
WikiEditor (Version 0.3.1)


Version: REL1_21-branch
Severity: major
OS: Windows 7

Attached:

wikierror.PNG (182×330 px, 8 KB)

Details

Reference
bz55994

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 2:23 AM
bzimport set Reference to bz55994.

korinek wrote:

formcode

Attached:

korinek wrote:

(In reply to comment #0)

Created attachment 13540 [details]
error

I got a Browser Error Message if I combine formedit, vector skin, wikieditor
on
freetext field and work with internet explorer. Firefox didn't show the
error.

This error has been reproduced on a new wiki install as well.
In my tests the first appearance seems to be in SemanticBundle-20130226.tgz.
SemanticBundle-20130929.tgz was OK.

Sry this must be... SemanticBundle-20130219.tgz was OK

Attached:

wikierror.PNG (182×330 px, 8 KB)

I just saw this now. Changing component to Semantic Forms, and re-assigning to me.

Alex - does this problem happen when using either the Chrome or Firefox browsers? Those two have much better Javascript error display.

korinek wrote:

i haven't tested chrome yet but firefox is not affected. I will test this issue begin next year under chrome. I ll keep you informed.

Alex - just checking up on this bug.

Yaron_Koren claimed this task.

I'm guessing that this has been resolved... feel free to reopen if not.