Page MenuHomePhabricator

VisualEditor: Transclusion inspector blank on opening some templates
Closed, ResolvedPublic

Description

Screenshot

See associated screenshot - this is for https://www.mediawiki.org/wiki/Template:Extension

When clicking the inspector icon, the window opens up but remains entirely blank and happily sits there like it for minutes* at a time. More worryingly, if I follow the normal workflow for a broken element (hit the X, make it go away, try and open it again) the inspector refuses to open at all, not just for that template but for other elements on the page.

*I gave up waiting; it may load, eventually, or never load.


Version: unspecified
Severity: normal
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=49797

Attached:

Details

Reference
bz49493

Event Timeline

bzimport raised the priority of this task from to High.Nov 22 2014, 1:43 AM
bzimport set Reference to bz49493.

Never loads. Trevor, is it selecting the wrong thing, so can't fetch it, or selecting the right thing, but can't fetch it for some other reason?

I found this as well. Here are the steps to reproduce:

  1. Open up [[mw.VisualEditor:Template test]] in edit mode.
  2. Click on any template, then click on the icon to open the template inspector.
  3. Click on the cross in the top-right-hand corner to close it.
  4. Click on the template inspector icon for the same template again. (It appears to still be there from the first time it was clicked.) This time the inspector appears blank.
  5. Click on the cross in the top-right-hand corner to close it again.
  6. Now, clicking on the template icon for any template on the page will have no effect (i.e. the template inspector doesn't load at all).
  • Bug 49862 has been marked as a duplicate of this bug. ***
  • Bug 49797 has been marked as a duplicate of this bug. ***

Related URL: https://gerrit.wikimedia.org/r/69806 (Gerrit Change I0b661744d0388345561897c9631f15e691737031)

  • Bug 49958 has been marked as a duplicate of this bug. ***
  • Bug 50016 has been marked as a duplicate of this bug. ***