But another part of the engineering work was focussed on re-plumbing a large chunk of the web clipper internals to match other work we are doing across all of the clients in support of improved reliability and sync. Part of our engineering work was focussed on the changes Apple had made in their plugin architecture. Prior to the 20th, we had thought we were on track. Apologies aren’t worth much compared to actions, but know that you have my apology for this. Even with the release date being pulled in, that shouldn’t have happened. When Apple released Safari on Sept 20th, we were surprised, we weren’t ready, and we ended up leaving you out in the cold. We had expected that Apple would release Safari along with macOS Catalina later in October.
This year for us has been all about making very hard decisions around competing priorities, and on this one, we erred. Because you’re rightfully complaining about something that should never have happened. It seems that they were not expecting the early update although I would have thought that they should have had this ready given the extensive beta programme.įor those also affected by this issue, there is a statement from one of their engineering team on their forum:įirst, I want to apologize that we’re all here. The forced update to Safari 13 has left Evernote with no workable extension for its clipper.
0 kommentar(er)
