Last modified: 2012-11-03 21:16:34 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 T35443, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 33443 - Multiple JavaScript issues in ext.smw.tooltips
Multiple JavaScript issues in ext.smw.tooltips
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: testme
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-12-31 08:57 UTC by Niklas Laxström
Modified: 2012-11-03 21:16 UTC (History)
4 users (show)

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


Attachments

Comment 1 Jeroen De Dauw 2011-12-31 18:20:18 UTC
I'm not seeing this locally. Can you link to where this happens?

I think the whole #info thing JS should be redone, the usage of wikibits is not the only thing that's bad about it :/
Comment 2 Niklas Laxström 2011-12-31 18:28:39 UTC
Have you set $wgLegacyJavaScriptGlobals to false? You should see this on translatewiki.net somewhere.
Comment 3 Jeroen De Dauw 2011-12-31 18:36:44 UTC
No I have not. I do get the error when I do though.

I don't have time to fix this, but it's not that hard to replace the current pop-up system with something nicer (jQuery based, auto sizing of popups, ect), so if you know someone who wants to poke at it, that'd be much appreciated. (As long as it's not committed before the 1.7 rel)
Comment 4 MWJames 2012-10-03 02:31:13 UTC
This https://gerrit.wikimedia.org/r/#/c/26341 might solve the problems.
Comment 5 MWJames 2012-11-03 09:36:09 UTC
Who changed to status to new and why? BubbleTT ... is no longer in use nor should the error message ...
Comment 6 Nemo 2012-11-03 10:12:22 UTC
(In reply to comment #5)
> Who changed to status to new and why? 

I did, because it was ASSIGNED

> BubbleTT ... is no longer in use nor
> should the error message ...
Comment 7 Nemo 2012-11-03 10:12:53 UTC
(In reply to comment #5)
> Who changed to status to new and why? 

I did, because it was ASSIGNED to nobody, which makes no sense.

> BubbleTT ... is no longer in use nor
> should the error message ...

Niklas, do you still see the error?
Comment 8 MWJames 2012-11-03 10:27:50 UTC
If at all this one should be set to resolved because the code that caused the error message and this pending bug report doesn't exists no longer within SMW 1.8 therefore the error message is rendered to be obsolete.
Comment 9 Niklas Laxström 2012-11-03 11:03:01 UTC
Let's close this then. We are running the latest version. Our javascript error collector is currently broken.
Comment 10 Andre Klapper 2012-11-03 21:16:34 UTC
(In reply to comment #8)
> If at all this one should be set to resolved because the code that caused the
> error message and this pending bug report doesn't exists no longer within SMW
> 1.8 therefore the error message is rendered to be obsolete.

"ASSIGNED to nobody" doesn't make sense so the mass-cleanup by Nemo_bis was very welcome, unrelated to the fact that anybody is free to retest old bug reports and close them if they don't apply anymore, like here.  Fixing the assignee doesn't imply also retesting the validity of every single report.
Anyway, thanks for updating this ticket by closing it! :)

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links