-
Notifications
You must be signed in to change notification settings - Fork 333
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get fullscreen working correctly in Safari #6
Comments
Also just noticed, in safari, that if you try going to fullscreen, and then revert back. all of the sudden the util bar will not show up, and even the keyboard shortcuts will not change between preview/editor anymore. |
Yeah, the utilbar and stuff is still broken going back on all browsers. If you can just get it looking ok in fullscreen all the reverting will look fine once im done with it unless you want to take a stab at the reverting of styles. |
alright, yeah i was going to try and get this one knocked out today. we'll see how it goes. |
I'm going to check for Safari in 0.1.2 and have it use the faux fullscreen since getting real fullscreen to work seems to be too hard. |
have the nasty fix in there for now. We'll need to open a new ticket if Safari ever gets fixed |
* upstream/develop: Ticket OscarGodson#96 - Make hash links scroll the iframe, not open a new browser window Ticket OscarGodson#6 - Shitty patch for Safari fullscreen. Using faux fullscreen until Safari gets fixed Prevent loading the editor when it's already loaded Typo in comment Ticket OscarGodson#161 - Remember the edit or preview state on unloading so when you load again its where you left it. Also added a guard for calling load when its already loaded to save on memory and changed all _eeState checks internally to use is() instead Ticket OscarGodson#88 - Added public is() method to check the state of EE. Added docs and tests and changed eeState to _eeState Conflicts: epiceditor/js/epiceditor.js epiceditor/js/epiceditor.min.js src/editor.js
Tested on Safari 6. Still works like shit... Updated the comment. |
…eryone elses, so update the comment to recheck when Safari 7 comes out.
It's pretty buggy right now for some reason:
The text was updated successfully, but these errors were encountered: