function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion

IDs and pageBlockButtons

This is a pretty minor issue but thougt I'd post anyway...

If I have a commandButton inside a pageBlockButtons section of a pageBlock with location left to the default of "both" then any ID I give the commandButton will be the same on the top button as the bottom button.

This is invalid HTML and means that I can't access that button from javascript.  IE and FF both behave much the same - they don't complain, but pick the top button only.

Anybody have a workaround?

You're right, and it should have been appending a "bottom:" to the ids in the bottom section.  I will log a bug for that.

Why not use two pageBlockButtons?

<apex:page id="thePage">
  <apex:form id="theForm">
      <apex:pageBlock id="theBlock">
          <apex:pageBlockButtons location="top" id="theButtons">
              <apex:commandButton value="click" id="clickMe"/>
          <apex:pageBlockButtons location="bottom" id="theBottomButtons">
              <apex:commandButton value="click" id="clickMe"/>

 then you can access both "thePage:theForm:theBlock:theButtons:clickMe" and "thePage:theForm:theBlock:theBottomButtons:clickMe".

Thanks - I always seem to miss the obvious workarounds.  That will do fine for now.