-
Bug
-
Resolution: Fixed
-
High
-
None
-
None
-
Safari Version 10.0.3 (12602.4.8)
-
1
-
Severity 1 - Critical
-
0
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Summary
JIRA Issue collector behaviour in latest Safari on OSX is confusing. This browser has disabled 3rd party cookies by default and despite the warning about this, you can still create issues. But when you hit the submit button you see another warning saying "there was a problem submitting your feedback". I.e.: you can't submit issues on Safari by default.
Steps to Reproduce
- Log in to staging Bitbucket (staging.bb-inf.net) with Atlassian account in Safari
- Go to Labs (tab on the left) and enable "Atlassian editor" integration
- Go to https://staging.bb-inf.net/owallhult/sverige/pull-requests/1/readmemd-edited-online-with-bitbucket/diff and try to add any comment. In the top right corner of the editor there's a "Feedback" button. Press it to open JIRA Issue Collector iframe.
Expected Results
- Warning about 3rd party cookies is brighter and "submit" button is either disabled or hidden at all.
Actual Results
- Warning about disabled 3rd party cookies is small and the submit button is still active
- When you click the submit button you see a confusing message (summary)
- is related to
-
JRASERVER-70494 Issue Collectors won't work for clients using Chrome 80 which enables new samesite cookie controls
- Closed
- relates to
-
JRACLOUD-64387 JIRA Issue Collector cannot create issues in Safari with disabled 3rd party cookies (submit button is still active)
- Closed