Last modified: 2014-02-28 14:53:46 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 T36660, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 34660 - Script tag within p, which may cause incorrect Facebook snippet
Script tag within p, which may cause incorrect Facebook snippet
Status: NEW
Product: Wikimedia
Classification: Unclassified
Fundraising (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: fr-tech@wikimedia.org
: fundraising
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-02-23 23:45 UTC by Matthew Flaschen
Modified: 2014-02-28 14:53 UTC (History)
5 users (show)

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


Attachments

Description Matthew Flaschen 2012-02-23 23:45:22 UTC
Boozerker reported on English Wikipedia VPT that Facebook was displaying JavaScript code as a snippet when people share a fundraising page (https://donate.wikimedia.org/wiki/Special:FundraiserLandingPage?uselang=en&appeal=Appeal-Sengai).  I saw in the source that the script element was inside a paragraph:

<p>
<script type="text/javascript">
$( document ).ready( function () {
  // Disable submitting form with return key
  $( 'form' ).bind( 'keypress', function(e) {
    var code = ( e.keyCode ? e.keyCode : e.which );
    if ( code == 13 ) return false;
  } );
} );
</script>

I don't know for sure if this is causing the incorrect Facebook snippet.  But it might be, and this could cause other issues.
Comment 1 Platonides 2012-02-24 17:49:14 UTC
We have head elements inside body there.
Comment 2 Andre Klapper 2012-12-17 01:05:09 UTC
Anybody willing to share this on Facebook to retest this, as it's that fundraising time of the year again? :)
Comment 3 Andre Klapper 2014-02-28 14:53:46 UTC
Resetting the assignee/status of this issue to default because there has been no progress in the last 12 months. Feel free to take it again when you are actually planning to fix this. Thanks.

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


Navigation
Links