Loading Profile...
Can't edit PBwiki 2.0 pages in Google Chrome (beta).
I know the Google Chrome beta pretty much just got released today (and it IS a beta), but I'll bring it up anyway just so that people are aware.
I'm able to edit and change 1.0 pages just fine. However, two 2.0 wikis that I use (one private, one public) are both uneditable in Chrome.
Safari apparently works with 2.0 wikis, judging from what I've read here. (Safari seemed to have the same problem, but that bug got fixed.) So, I'm less inclined to think that it's some odd WebKit bug, if that helps, though I wouldn't know for sure.
I'm able to edit and change 1.0 pages just fine. However, two 2.0 wikis that I use (one private, one public) are both uneditable in Chrome.
Safari apparently works with 2.0 wikis, judging from what I've read here. (Safari seemed to have the same problem, but that bug got fixed.) So, I'm less inclined to think that it's some odd WebKit bug, if that helps, though I wouldn't know for sure.
I’m somewhat sobered by the discovery.
6
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?Thanks for pointing this out- we're aware of the issue and looking into it!
-
Inappropriate?Yup! We discovered this as soon as we downloaded it too... we suspect that it's an issue with V8 and not necessarily WebKit.
I’m glad other people are using Chrome.
-
Inappropriate?bump :-) -
Inappropriate?Just found this out a bit ago, but my Chrome seems to be working with PBwiki 2.0 now. Didn't test a lot of the editor's features out yet, but I can edit my and save my pages fine now.
Either this is because...
1.) PBwiki changed things on their end to allow Chrome's V8 to work properly, or...
2.) The development build I'm using (0.3.154.3) fixed it on Chrome's end.
Either way, something is happening that's making both ends meet. Yay~
I’m somewhat excited.
1 person says
this solves the problem
-
Inappropriate?Yes, I can confirm this! Suddenly, it started working in Chrome yesterday or day before; don't precisely recall. My guess is your #1 is more likely as I am using Chrome 0.2.149.30 ... AppleWebKit/5.25.13
Thanks for reminding me to update here!
I’m ecstatic
EMPLOYEE
EMPLOYEE
