Regarding this section of includes/specials/SpecialExport.php,
header( "Content-type: application/xml; charset=utf-8" );
if( $wgRequest->getCheck( 'wpDownload' ) ) {
// Provide a sane filename suggestion $filename = urlencode( $wgSitename . '-' . wfTimestampNow() . '.xml' ); $wgRequest->response()->header( "Content-disposition: attachment;filename={$filename}" );
}
For me, I would expect two different responses in the users' browser:
- if the wpDownload box is checked, the browser would insist they
save the response in a file, and would not show them anything on the
screen.
- if the wpDownload box is NOT checked, the browser would show them
the same contents directly.
This all works fine if one uses Firefox, but in midori, emacs-w3m,
etc. browsers I tested here on Debian GNU/Linux, one just gets for 1
and 2 the same mishmosh of semi rendered mess.
Yes, this is all the fault of those browsers not being up to date with
the trends of today, but I still propose you instead make the
wpDownload choice a radio button with additional choices:
- "send as text/plain, for guaranteed visibility in ones browser"
- "send as application/download or application/octal-stream or
something, for guaranteed forcing the browser to save in a file"
Of course the default checked item should still be like 1) above.
Version: 1.13.x
Severity: enhancement