Ok - Thanks for explaining Eric However I don't know how to test if the problem still exists in Safari - or in Chrome, for that matter. If I can test it by changing a line in the plugin - please tell me and I will try.
YS Måns Mårtensson On 5 Okt., 20:50, Eric Shulman <[email protected]> wrote: > > config.options.chkSinglePagePermalink= true; > > Doesn't seem to work in Google Chrome as it does in FF.... > > How do I make it work? > > This settings causes a browser crash in Safari, so it is disabled for > that browser. However, the 'browser sniff' for Safari based upon this > test: > > config.userAgent.indexOf("applewebkit") > > Because Chrome is also built using 'webkit', it is possible that it's > userAgent value also contains the 'applewebkit' text. Thus, as far as > TW is concerned, Safari and Chrome are indistinguishable, and thus the > SinglePageModePlugin's bypass of the permalink feature is applied for > either browser. > > It's possible that this crash bug no longer exists in Safari (or at > least does not also exist in Chrome). If this is the case, then I can > remove the bypass in the plugin and re-enable automatic permalinks > when using Safari and Chrome. If this the problem still exists in > Safari, but not in Chrome, then I will need some definitive way of > recognizing Chrome, separate from Safari, so I can re-enable > permalinking for Chrome, but not for Safari. > > -e --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en -~----------~----~----~----~------~----~------~--~---
