Allow +1 Button Targeting Anchors within Pages

[GoogleCodeExporter]

I wish to implement multiple +1 buttons on a single webpage, each of them 
pointing to different URLs that will bring them to anchors on that page.  

It is my understanding that anything beyond the # character in the target URL 
is stripped when the +1 button is rendered.

I think it would be great to also be able to create multiple +Snippets for each 
targeted anchor on the webpage.

Original issue reported on code.google.com by ria.gala...@gmail.com on 4 Oct 2011 at 1:40

[GoogleCodeExporter]

Issue 59 has been merged into this issue.

Original comment by chirags@google.com on 2 Nov 2011 at 12:10

[GoogleCodeExporter]

For sure. I need this also.

Original comment by danield...@gmail.com on 2 Nov 2011 at 3:35

[GoogleCodeExporter]

This obviously affects AJAX websites in a BIG way, since you would have URL:s 
using the 

  /#!/path_or_identifier

pattern recommended by Google. I would say it should have priority HIGH

Original comment by jhsw...@gmail.com on 8 Dec 2011 at 8:59

[GoogleCodeExporter]

Original comment by mimm...@google.com on 4 Feb 2012 at 1:14

• Changed title: +1 Button Targeting Anchors within Pages via she-bang urls
• Added labels: Component-Plugins

[GoogleCodeExporter]

Here's my use case: my site has a page that lists classes and another page that 
lists instructors. I want browsers to be able to +1 a class or instructor 
without +1'ing the page itself. Bring able to +1 anchor (link) targets would 
address this nicely.

Original comment by don.bart...@gmail.com on 16 Feb 2012 at 9:55

[GoogleCodeExporter]

I've been trying to figure out this issue for the whole day today... This 
feature would be the easiest solution to my problems. 

I have a blog-type of a photo gallery website and I'd like to allow people to 
+1 specific photos, but I can only refer to them through URL anchors! the +1 
google button +1s the whole page, so I cannot have the +1 counters work 
independently for each photo (unless I make a separate page for each photo, 
which is 150 new webpages <:( )

Original comment by stan.nik...@gmail.com on 24 Mar 2012 at 6:53

[GoogleCodeExporter]

I fixed this issue in my case by using ? instead of # and mimicking the default 
anchor behavior with javascript. 

Original comment by eric.j.s...@sadasystems.com on 26 Mar 2012 at 4:04

[GoogleCodeExporter]

If you use the Ajax crawling specification you can use hash-bangs.

For example, the following works just fine:

<g:plusone size="tall" annotation="inline" 
href="https://twitter.com/#!/lindner"></g:plusone>

This results in a request like this:

  https://twitter.com/?_escaped_fragment_=/lindner

Original comment by plindner@google.com on 25 Mar 2013 at 11:34

[GoogleCodeExporter]

Original comment by joannasm...@google.com on 11 Apr 2013 at 4:01

• Changed title: Allow +1 Button Targeting Anchors within Pages
• Added labels: Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect