Re: iOS 10 not showing editor buttons
Reply #77 –
sorry if I insist on this, but are there any news?
one of my moderators told me that is happening with all browsers in ios 10: safari, chrome and also firefox.
Re: iOS 10 not showing editor buttons
Reply #78 –
If not all is facing this, it could be just a caching issue.
Re: iOS 10 not showing editor buttons
Reply #79 –
You are right to insist, but I really have no idea what is going on, neither means to investigate it.
Unless someone with an iOS10 device is able to debug the issue we are stuck...
Is the PM editor working?
Re: iOS 10 not showing editor buttons
Reply #81 –
I was planning to help with my ipad mini 3 with iOS 10 but according to my research, to enable debugging mode , you'll need an apple computer. I don't have this. So, couldn't help debugging unless I can enable it.
About the caching, I don't mean for you to disable it, but rather, clear your cache and try again. May be from both browser and ElkArte sides.
Re: iOS 10 not showing editor buttons
Reply #83 –
I finally managed to get a 10.12 Sierra running inside a Virtual box on my windows machine. I'm not sure its all that stable but it does seem to run. I don't know if this is a mobile only issue or if it will show up on the desktop version as well, so if someone with the issue can give me a test account I'll try this vbox to see if I get the error.
Re: iOS 10 not showing editor buttons
Reply #86 –
I have a chance to swipe jquery.sceditor.bbcode.min.js file in 1.0.9 with the one in 1.1 Beta 3 just now and the editor surprisingly shows back all the icons and emoticons. I will try the suggested debugging technique mentioned above soon and report the errors in the current 1.0.9 file, if I managed to get the debugging mode working.
Re: iOS 10 not showing editor buttons
Reply #89 –
I started to debug this this morning and when it all wired up, I noticed the ipad battery is now only 10%. Meh... I'll try again after it is duly charged.
Just to be sure, I should look into the missing bbccode icons and emoticons errors, right?
Some other questions, I noticed the code is quite old (1.4.5) and there could be a bug in it as reported in samclarke github. Currently is 1.5.1 and our our beta 3 is 1.5.0. Why not upgrade it for 1.0 branch as well? In any event, we are merely using it rather than making any custom changes to it, right? (or no?)