Error with paid event registration pages - Chrome browser only

[joemcl]

Here's problems that occur with paid event registration pages that *only* occur when using the Chrome browser - IE and Firefox work fine.
1. We've created a profile that captures billing address info for a paid event - see https://my.citizenactionny.org/civicrm/event/register?reset=1&id=327 . When you click one ticket option, the total price changes, but it isn't until a second price option is clicked, or that first price option is unchecked, that the credit card info fields appear. This is an issue because if you just go to the page, select a single ticket option, fill out the rest of the form and hit continue, the form returns an error that you haven't filled out the credit card fields.
2. If we hadn't adjusted the profile to capture billing address info, the form would never request billing address info and therefore continually return a required field error saying that billing address fields are required, but those fields would never be displayed.
We believe our Civi installation formerly automatically added billing address fields for any form that collected payment (in the same way that it does on contribution pages). I'm not saying that's good - we actually like it better this way to be able to include those fields in the profile so it's one logical and coherent set of fields. But the display of the credit card fields only after clicking around a number of times isn't ok and needs to be fixed.
The form is functional as it is now, but that error is really confusing and could easily lead to people having registration problems. And many people nowadays are using Chrome.
Because this is a paid event page, I'm not going to try and duplicate it on the demo.civicrm.org page (unless there is a way to use a dummy or Test payment processor account on demo, I'll check it out).
We've asked Google for help, but nothing so far.
Thoughts?

[Michael McAndrew]

Because this is a paid event page, I'm not going to try and duplicate it on the demo.civicrm.org page (unless there is a way to use a dummy or Test payment processor account on demo, I'll check it out).

you can do - I would try and replicate on demo and report back.

[Eileen]

We patched this on 4.4 & will look to put the fix into an LTS release - these issues relate. It is currently  fixed in 4.5 & in the fuzion repo

https://issues.civicrm.org/jira/browse/CRM-14882
https://issues.civicrm.org/jira/browse/CRM-15432
https://issues.civicrm.org/jira/browse/CRM-15433

[joemcl]

Eileen thanks so much for the fix and the update here