function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
TopalovichTopalovich 

OutputLink element inserting contents of 'Value' attribute in HTML anchor tag

 

Another issue that just popped up after the Winter '12 upgrade is that I noticed that the apex:outputLink element, when there is no text between the opening and closing tags, will by default render the value of the 'value' attribute (i.e. the URL being referenced) as visible text in the HTML anchor tag.

 

 

So this code:

 

<apex:outputLink value="http://forcearchitects.deliveredinnovation.com" title="Force Architects: Cloud Computing and Salesforce Architecture Blog by Delivered Innovation" target="_blank" styleClass="menu_blog" rel="nofollow" />

 

Renders this HTML:

 

<a class="menu_blog" target="_blank" title="Force Architects: Cloud Computing and Salesforce Architecture Blog by Delivered Innovation" rel="nofollow" href="http://forcearchitects.deliveredinnovation.com">http://forcearchitects.deliveredinnovation.com</a>

 

While this code:

 

<apex:outputLinkvalue="http://forcearchitects.deliveredinnovation.com" title="Force Architects: Cloud Computing and Salesforce Architecture Blog by Delivered Innovation" target="_blank" styleClass="menu_blog" rel="nofollow"> _ </apex:outputLink>

 

Renders this HTML:

 

<a class="rssLinkSprite" target="_blank" title="Subscribe to Delivered Innovation with RSS" rel="nofollow" href="http://feeds2.feedburner.com/forcearchitects"> _</a>

 

 

 

The behavior prior to the Winter '12 upgrade was to simply render an empty anchor (the hyperlink is on the container element).  Now it inserts the full URL as text in the anchor tag.  Is this the new expected behavior of the element?  I don't see any documentation spelling this out.

 

cwall_sfdccwall_sfdc

Yes, this is new behavior.  We are evaluating.  Please stay tune.
TopalovichTopalovich

Any recommendation for a workaround (just adding blank spaces still causes the URL to be displayed as text)?  Our website looks really bad right now (although I am relieved I found a workaround for the issue that brought it down completely).  

 

Any idea why this change would be applied retroactively to prior API versions rather than 23.0 and forward to preserve backward compatibility?

 

 

Thanks,

 

Mike

 
MattSchulze@ca.comMattSchulze@ca.com

Any update on this issue?
TopalovichTopalovich

Nothing, yet.  If I haven't heard anything by EOD, I'm going to have to start going through all VisualForce pages and replacing the OutputLinks that are exhibiting this behavior with regular HTML anchor tags because our website has looked like crap all week and I can't wait forever.

 

 

Mike