Last modified: 2012-04-16 09:16:05 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 T32937, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 30937 - When a page is blocked from display due to $wgEditPageFrameOptions, it should at least display an error message
When a page is blocked from display due to $wgEditPageFrameOptions, it should...
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
unspecified
All All
: Unprioritized enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-09-16 19:23 UTC by Ryan Kaldari
Modified: 2012-04-16 09:16 UTC (History)
1 user (show)

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


Attachments

Description Ryan Kaldari 2011-09-16 19:23:05 UTC
Right now when display of a special page is blocked due to it being in a frame and $wgEditPageFrameOptions being set to DENY or SAMEORIGIN, nothing is output at all. This gives developers the impression that something is broken rather than hidden on purpose. It would be nice if an error message were displayed in these cases. Something like "This page cannot be displayed within a frame." or something similar.
Comment 1 Daniel Friesen 2011-09-17 01:58:50 UTC
X-Frame-Options is an instruction to the browser. There is no interface that lets a server understand if a page is being loaded in a frame, only an instruction to tell a browser to not load a page in an iframe even though it's loaded everything.

The browser is the only one capable of displaying a warning like that. This isn't a bug in MediaWiki because it is the browser that is displaying the frame as blank like that and we have no control over it.

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


Navigation
Links