Last modified: 2014-01-19 02:24:21 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 T62207, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 60207 - expandTemplate doesn’t create a new frame
expandTemplate doesn’t create a new frame
Status: RESOLVED DUPLICATE of bug 55525
Product: MediaWiki extensions
Classification: Unclassified
Scribunto (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
https://test2.wikipedia.org/wiki/Mult...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-01-18 16:22 UTC by Seb35
Modified: 2014-01-19 02:24 UTC (History)
3 users (show)

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


Attachments

Description Seb35 2014-01-18 16:22:23 UTC
When a Lua module uses the function frame:expandTemplate, this doesn’t create a new frame (contrary to frame:preprocess) but expand the template in the "top" frame (the parent frame of the expanded template is the top frame).

I guess this is a bug since the "parent frame" is defined as the "the frame for the page that called {{#invoke:}}" ([[mw:Extension:Scribunto/Lua reference manual#frame:getParent]]).

I created some pages to illustrate this behaviour on https://test2.wikipedia.org/wiki/Multiple_transclusion. It can be remarked also that if you again transclude the "Multiple transclusion" page, the first case shows the new top frame.
Comment 1 Brad Jorsch 2014-01-19 02:24:21 UTC
(In reply to comment #0)
> When a Lua module uses the function frame:expandTemplate, this doesn’t
> create a
> new frame (contrary to frame:preprocess) but expand the template in the "top"
> frame (the parent frame of the expanded template is the top frame).

A new frame *is* being created, but it's getting the wrong title and isn't a child of the frame it should be a child of.

While it's not exactly obvious, this is the same as the problem in bug 55525.

*** This bug has been marked as a duplicate of bug 55525 ***

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


Navigation
Links