Theme 11, live scope for dynamic action not working in IE

Question

Hello all,
I use theme 11, and I have a dynamic action on page 0 that fixes a region width, because it is too long to match the page width. I set the Event Scope to "live" because the region is a report and it has many rows and pagination is needed. When I have to go to page 16-30 from 1-15 and if there is a record which is longer than the current 15, page is partially refreshed and the width is changed, but that works for Mozilla and Chrome. In IE the dynamic action from page 0 is not triggered, in spite of the live event scope and I don't know why. Is there a way I can fix that problem?
Thanks in advance!

Answer 1

Hi Ivan,
Thanks for the information, this is indeed an interesting case. I'm assuming you have 'Enable Partial Page Refresh' in the report attributes set to 'Yes'. Please let me know if this is not the case.
I don't think an event of 'Page Load' with a scope of 'live' is correct. The 'live' event is a way of saying, attach some behaviour to something on a page (eg a delete icon in a report row is clicked), and keep that behaviour 'alive' even if that part of the page is updated (eg the report paginates with PPR to the next set or results, and clicking on the delete icon in the report still works). However here, when the event is page load, I don't think specifying 'live' will do what you want.
What I think you're really interested in is indeed when the page first loads, but then when the report is refreshed via PPR. Therefore, I would try the following:
1) Change the dynamic action event to 'After Refresh'.
2) Select the report region from the 'When > Selection' attributes (ensuring your report template contains a id="REGION_STATIC_ID" attribute, otherwise the DA won't work).
3) In your 'Actions', ensure the 'Fire on Page Load' checkbox is checked.
So this says do the action when the page loads, then always after the report is refreshed via PPR. This will fire after pagination, sorting or a dynamic action refresh.
Interestingly (at least in my mind!), you can actually set the event scope back to 'bind' here. This is because as part of the DA framework, we purposefully attach the event handlers for report handling to an element that is not updated during PPR for pagination or sorting, it's higher up in the DOM tree. This gives slightly better performance than having to use 'live', which is more expensive computationally and yet still keeps the registered behaviours.
Also something else which may help, you can check if the DA is firing when expected by using a JavaScript console (eg in Chrome native Developer tools, Firebug with Firefox), with application debugging enabled (Application Properties) and switched on (via developer toolbar). Load the JS console, and you'll be able to see when the DA fires.
As far as the actual IE specific logic goes, I haven't looked into that too much yet, because I felt it was more important to get the DA firing correctly first, then see where we're at.
Regards,
Anthony.
Edited by: Anthony Rayner on Nov 14, 2011 11:06 PM