Odd situation with Safari after enabling account expiration and locking

Question

Hi team,
i found the following puzzling situation today.
I enabled account expiration and locking in a workspace, thereafter all end users were requested to change their password as soon as they attempted to login to the application.
Some of these users went through this process smoothly and after changing the password they could log in. Others apparently succeeded in changing the password but the password change process is triggered again and again.
These users are receiving the following message after clicking on "apply changes" (p50 of app 4155).
ERR-1777: Page 50 provided no page to branch to. Please report this error to your application administrator.
When clicking on "restart application", they get the following additional screen:
You have successfully logged out. You have been redirected here after using a logout link provided by an authentication scheme. To redirect to a page in your flow instead, do something like this:
Create a page in your flow and give it an alias PUBLIC_PAGE.
On the Flow Builder page attributes page, select the "Yes - This page is public" Public Page attribute.
Change the logout URL in your authentication template to redirect to this new page after the logout procedure executes. For example, using the API, make your logout URL:
wwv_flow_custom_auth_std.logout?p_this_flow=&FLOW_ID&p_next_flow_page_sess=&FLOW_ID:PUBLIC_PAGE:&SESSION
Note that the suggested URL uses a somewhat outdated syntax lacking the period after the application items, so you might want to revise it for future releases.
After various tests it turned out that the problem is in the browser (don't ask me what).
Safari users do not succeed in changing their passwords through page 4155:50, while Firefox users do.
I have a password change page inside my application though and everybody can change their password from there successfully.
Also, after changing the password using Firefox, Safari users can log in without problems whatsoever.
So the final question is: what's wrong with page 50 of application 4155 when run from Safari on Mac?
It happened with Apex 3.1.2 and Safari Version 3.2.1 (5525.27.1)
Thanks!
Flavio
http://oraclequirks.blogspot.com/search/label/Apex

Answer 1

Scott,
that was exactly what i was about to do yesterday night, but at the post office i realized i didn't know the address :D
Then, fortunately for me, but regrettably for you (hehehe), i realized that Safari is not the culprit.
For some reason people using Safari were always submitting the page with enter, while Firefox users were submitting with the button.
I made a test and Safari is fine as long as you click on the button, the bug is in the submit through the enter key.
Thanks and sorry about the mac air, may be the next time!
Flavio
PS: aren't you coming to ODTUG Kaleidoscope?