Skip to content
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

Safari Bug #29

Open
dpogni opened this issue Feb 22, 2016 · 6 comments
Open

Safari Bug #29

dpogni opened this issue Feb 22, 2016 · 6 comments
Assignees
Labels

Comments

@dpogni
Copy link

dpogni commented Feb 22, 2016

I'm having an issue in Safari. When I'm attempting to edit a page that has wysiwyg enabled, the browser will franticly refresh. I've looked into the JS file, but can't seem to figure out how to fix.

I was able to recreate the issue in a fresh install of kirby and kriby-wysiwyg.

Kirby 2.2.3, Safari 9.0.3

@good-idea
Copy link

+1 with Panel 2.2.0 Safari 9.0.3

@puppycodes
Copy link

+1 Meeee too Panel 2.2.0 Safari 9.0.3

@good-idea
Copy link

I traced this back to line 113 of wysiwyg.js:

        self.$field.bind('destroyed', function() {
              self.editor.deactivate();
        });

Commenting out self.editor.deactivate() stopped the refreshing.

The deactivate function is buried in the minified jQuery UI ~ so my investigation comes to a close ~

@puppycodes
Copy link

yessssss!!💃🏻

On Feb 27, 2016, at 12:14 AM, SQbiz notifications@github.com wrote:

I traced this back to line 113 of wysiwyg.js:

    self.$field.bind('destroyed', function() {
          self.editor.deactivate();
    });

Commenting out self.editor.deactivate() stopped the refreshing. Maybe it has something to do with the 'destroyed' event? but that seems less likely.

The deactivate function is buried in the minified jQuery UI ~ so my investigation comes to a close ~


Reply to this email directly or view it on GitHub.

@JonasDoebertin
Copy link
Contributor

Needs some further investigation. I'll keep this open for now.

@JonasDoebertin JonasDoebertin self-assigned this Mar 2, 2016
@dgdsp
Copy link
Contributor

dgdsp commented Aug 4, 2016

should be fixed in dev-branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants