Last modified: 2011-06-05 12:28:33 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 T21474, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 19474 - Geshi CSS styles not included in Code Review
Geshi CSS styles not included in Code Review
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
CodeReview (Other open bugs)
unspecified
All All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
http://www.mediawiki.org/wiki/Special...
:
: 27710 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-07-02 08:51 UTC by Niklas Laxström
Modified: 2011-06-05 12:28 UTC (History)
5 users (show)

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


Attachments

Description Niklas Laxström 2009-07-02 08:51:06 UTC
Is the parser output only partially used?
$parser->mOutput->addHeadItem( self::buildHeadItem( $geshi ), "source-{$lang}" );
Comment 1 Brion Vibber 2009-08-04 21:52:21 UTC
Not sure I understand this; geshi syntax highlighting isn't used on this page that I can see, so it's not surprising that the geshi styles aren't being pulled in?

Comment 2 Niklas Laxström 2009-08-05 06:40:01 UTC
When using <source> tags in review comments, they are not coloured.
Comment 3 Brion Vibber 2011-01-22 18:19:54 UTC
The HTML output for comments is fetched via $wgOut->parse(), which throws away any head items or ResourceLoader modules specified in the ParserOutput object.

Without redoing the entire output code for the code review pages, this might work:

* change out $wgOut->parse() for 
* call $wgOut->addParserOutputNoText($parserOutput) to add styles/etc
** note this will pass through language links and category links as well. Alternate: just do the head items/addModules but this feels icky. 
* fetch the HTML with $parserOutput->getText() and use as before
Comment 4 Sam Reed (reedy) 2011-02-25 16:05:40 UTC
*** Bug 27710 has been marked as a duplicate of this bug. ***
Comment 5 Sam Reed (reedy) 2011-03-19 01:37:50 UTC
(In reply to comment #3)
> The HTML output for comments is fetched via $wgOut->parse(), which throws away
> any head items or ResourceLoader modules specified in the ParserOutput object.
> 
> Without redoing the entire output code for the code review pages, this might
> work:
> 
> * change out $wgOut->parse() for 
> * call $wgOut->addParserOutputNoText($parserOutput) to add styles/etc
> ** note this will pass through language links and category links as well.
> Alternate: just do the head items/addModules but this feels icky. 
> * fetch the HTML with $parserOutput->getText() and use as before

Care to elaborate a bit more Brion?

Was just looking at this, and the idea doesn't seem complete...

ie Which parser output instance you are using, etc

Ta! :)

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


Navigation
Links