![]() ![]() ![]() In the coming months we'll be communicating these improvements out to you, to help everyone understand what the process actually is, when you can expect to hear back about feedback you've provided, and how user feedback influences the roadmap. We're currently working with our product operations team to redefine our policies and processes. There are big changes coming to our community experience later this year, and the top item on the priority list is overhauling how we intake and communicate about feature requests and product feedback. We have a lot of work to do to build up trust and transparency with this community. It's a frustrating experience on both sides. And you're right, we've not managed the product feedback conversations well for many years. We're engaging with product and engineering teams across the company to make sure we untangle the foundation to better rebuild. The host mapping feature within Zendesk was designed and implemented in a way which fundamentally relies on third-party cookies to work, and therefore eliminating our use of them is not a simple change for us to make on our own. It has taken longer than it should have to remove the reliance of third-party cookies within Zendesk and we're treating this issue internally with a very high priority. We've rolled out a similar Storage Access API solution to Firefox browsers for all customers. We resolved this by implementing the Storage Access API and had to introduce some additional steps for the login process in order to comply with Safari's implementation of the Storage Access API. We know that blocking third-party cookies is a change that's being rolled out to more and more browsers, and it previously did completely break our login page on Safari for host-mapped accounts. It's our intention and goal that this removes any issues introduced by browser restrictions on third-party cookies and cross-site requests. We are taking the time in 2021 to completely eliminate our use of third-party cookies across our platform. We've heard the concerns about how Zendesk works with browsers that block third-party cookies. Not the most elegant solution, but it's better than having to keep opening another browser specifically configured with less safe settings just to be able to access Zendesk. Once it reloads without the warning, I just turn the restrictions back on again. You can now disable the "Disable Cross-Origin Restrictions" to return Safari to its safe state, and in my case, I've been able to use Zendesk fine during that session.Ĥ) It does seem that I need to enable "Disable Cross-Origin Restrictions" each time I sign in, but that's only for that sign-in page. It should then return to the main sign-in page without the warning. It will ask you if you want to allow the site (likely something like ) to allow cookies from another domain (zendesk). After more than a year of no longer having Zendesk access due to this issue, even following the updated directions of the article above, I was able to get it working by doing the following:ġ) In Safari menu, select "Preferences" and then click on the last tab "Advanced" and select the last item in the bottom "Show Develop menu in menu bar."Ģ) When on your Zendesk login page with the "Cookies required" warning across the top of the page, select Menu > Develop > Disable Cross-Origin Restrictions:ģ) Now click on the "Continue" link in the yellow warning box in the login page. ![]()
0 Comments
Leave a Reply. |