WebDialog.set_html fails under Safari 5.0.6

Dan Rathbun

Cursed - this is more troublesome than I thought.
Under Windows I can clean up all temps by using AppObserver.onQuit - but under OSX it appear to never trigger.

So then there's no way under OSX that my proposed workaround for the Instance Observer can work for SU8.

Makes me wonder if "they" just turned off the onQuit() callback (for OSX,) as a 'quick-temporary-fix' for the BugSplat! on close issue?

thomthom

@dan rathbun said:

Makes me wonder if "they" just turned off the onQuit() callback (for OSX,) as a 'quick-temporary-fix' for the BugSplat! on close issue?

hm... when was that fix issued? I'd like to try with an older SU to check.

Dan Rathbun

@thomthom said:

@dan rathbun said:

Makes me wonder if "they" just turned off the onQuit() callback (for OSX,) as a 'quick-temporary-fix' for the BugSplat! on close issue?

hm... when was that fix issued? I'd like to try with an older SU to check.

I am speculating... remember during v8 beta the Instance Observer OSX BugSplat! on close without saving the model first?
It was not fixed for 8.0M1.

However you have that onQuit() works for v7.1 on OSX.

thomthom

I tried onQuit and at_exit on OSX SU 7.1.6859 and I could not get them to trigger either...

Dan Rathbun

It's a bit confusing to have your Observer table combined with both platforms, have you thot about having a table for each platform?

Dan Rathbun

And just to be clear, your testing using the Ruby ver that ships with the Sketchup version? (v1.8.5-p0)

What happens if your change the Sketchup Ruby symbolic links on the Mac to a newer Ruby install (v1.8.6-p287 or higher?)

Dan Rathbun

And also you might try to trap the SystemExit exeception, which is supposed to be called, unless Google used exit!() in which case your out of luck.

I'm not sure if Kernel.set_trace_func will catch a call to exit!() or not.

thomthom

@dan rathbun said:

It's a bit confusing to have your Observer table combined with both platforms, have you thot about having a table for each platform?

Wouldn't having two tables make it harder to get an overview of what observers has issues?

@dan rathbun said:

And just to be clear, your testing using the Ruby ver that ships with the Sketchup version? (v1.8.5-p0)

What happens if your change the Sketchup Ruby symbolic links on the Mac to a newer Ruby install (v1.8.6-p287 or higher?)

Yes - I only test SketchUp out of the box. And that is complicated and time-consuming enough...

Dan Rathbun

I wish someone could make a one-click dmg installer for Sketchup Mac that would bring their Ruby up to par with the PC edition.

fredo6

The problem seems to be in all versions after 5.0.6

A user encountered the problem on Safari Version 5.1 (7534.48.3): images not shozing and Update (via xmlhttprequest not working)

Fred

Pout

I'm a bit confused here.

So if you would use set_file then all should work fine?
I'm using that method and it loads a html file but the linked js files inside do not seem to work.
They do however work when just opening the html file with Safari. (So not in a webdialog)

thomthom

@pout said:

I'm a bit confused here.

So if you would use set_file then all should work fine?
I'm using that method and it loads a html file but the linked js files inside do not seem to work.
They do however work when just opening the html file with Safari. (So not in a webdialog)

Yes, set_file should work. Got a sample of what is not working?

Pout

here you go
unzip, put the rb in plugisn and the Grid directory to
thx for testing!

test.zip

Pout

and in SU you can launch by TESTOLA.testing in ruby console

driven

With your WebDialog in Safari 5.0.6 Web Inspector shows this error

TypeError: 'null' is not an object (evaluating 'navigator.userAgent.match(/(?:KHTML\D*|VERSION\D*)(\d[\d\.]+)/i)[1]')

I'd look into that to start.

john

thomthom

hmm... why are you sniffing the userAgent string? It's preferred to test for features instead of testing the user agent string.

Pout

Well it is in fact not a script written by me.
It is an external script which i'm trying to incorporate.
So the complete js side is unclear to me.
In what file is the error located?

Thx again

driven

@pout said:

In what file is the error located?
Thx again

GridE.js
It's in encodedstring LZD="....."

which I can't look at.

john

Pout

driven, thx!!
I have reported the error an already received a debugged version (bug at their side)