This functionality has been made private with the move to a jQuery UI widget. That whole paper's part on JS can actually simply be disregarded. The only public functionality is "refresh" and reading some (useless to us) options. And well, these last 2 sentences actually:
Well, not much to review since it'd all be broken and near unfixable anyway.
Yeah, well. I don't think anybody expected wild things anyway.
This happened to most other functionality which you could previously access through gReport. And there is no 'clean' way to fix this right now (call a method on the widget). Much like "paginate": https://community.oracle.com/message/13017402#13017402
You can actually do the same as I did there bar some changes. See here ==> https://apex.oracle.com/pls/apex/f?p=90922:9:0::::: (set ir view mode)
The other thing you can do:
1) make sure the detail button is visible (option set to yes in the designer)
2) emulate a click on it, along the lines of
I'd really like to lament not having more public functions available but that's where it stands right now. I understand how gReport was probably used all over the place and how some things were exposed that maybe shouldn't have, but right now I feel we've lost some power. I don't see how having to do these click events is in any way more safe than having used gReport. I actually feel disappointed. I'd not expect to have everything opened up publicly, though here was a chance to do so properly and in a controlled way instead of boxing everything in. Oh well, must be me.