Browser Coompatibility

[joseppic]

Hi,

I've just put some files out on Web Companion.

It seems that the Filemaker Record Navigation and some Filemaker Side Menu options are missing in: Mozilla 1.3 Netscape7 but are working in IE5.

Is this a CSS2 issue?

My people use a mixture of browser and platforms, does anyone have advice as to which browsers are compatible?

Can someone direct me to docnn which can guide me thru which scripts work and which don't too please - I'm not able to launch scripts which are behind buttons

within a portal.

thanks for your continued help,

J.

[Unable]

Instant Web Publishing requires a database design solution. The db must be properly constructed since the HTML is written by FMPro on the fly. WYSIWYG.

You may find some useful information in the TechInfo Database at FileMaker. I use it a lot for CDML and Custom Web Publishing - which it the way to go.

Good luck (you're going to need it with IWP).

[Anatoli]

RE: I'm not able to launch scripts which are behind buttons

IWP or CWP -- read about single threaded FM and problems with scripts triggered from browsers.

[Peter Kyme]

joseppic said:

Hi,

I've just put some files out on Web Companion.

It seems that the Filemaker Record Navigation and some Filemaker Side Menu options are missing in: Mozilla 1.3 Netscape7 but are working in IE5.

Is this a CSS2 issue?

I am also experiencing this - we have purchased Filemaker Unlimited in order to use the web companion sharing (so non-technical staff can do the page design).

It seems that the web companion interface doesn't support Mozilla, or any of the browsers based on it for that matter. This is a big deal, since we have a large amount of Linux, Mac OS 9 & X and Windows machines that all need to access this material.

Does anyone know if there is a workaround for this that doesn't involve going to custom web publishing? It seems extraordinary that Filemaker Inc. haven't updated their web companion javascript to ensure compatibility with Mozilla.

Thanks in advance,

Peter Kyme

[Unable]

"Does anyone know if there is a workaround for this that doesn't involve going to custom web publishing?"

IWP = WYSIWYG,

IWP = WYSIWYG,

IWP = WYSIWYG ("anything I say three times is true", Alice).

If you are experiencing problems with IWP is it because your intuition has not allowed you to design your database(s) to take advantage of the WSYIWYG features of FMPro's IWP. Shame on you for being a bad designer (this is facetious and do not take it personally, please).

FWIW, FMI has a postiton paper which states in effect that they are a database solutions company and that they have done quite enough (thank you) in the field of the www. If you are turly energetic you can research their website for this statement.

So short of going to CWP, the answer is in your abilities as a FMPro database developer to find what information is available about IWP (such as recognized scripts - which information ignores the single-thread nature of ScriptMaker and its inherent problems) and intuit a solution compatable with WYSIWYG.

Consider, if you will, the multitude of threads in these forums which are devoted to CDML.

I guess it ain't that easy no matter which road you travel.

Best of luck with your new database design goals.

I'll take CDML and all its problems any day.

Or you could just buy a bunch of licenses and do it peer-to-peer. Perhaps a committee should be formed...

[kenneth2k1]

Wouldn't ya know it, the manual has a section "About browser requirements." Read chapter 14 in the manual, particularly from 14-11 on.

There might be something here to give you some answers.

Ken

[Anatoli]

RE: Does anyone know if there is a workaround for this that doesn't involve going to custom web publishing? It seems extraordinary that Filemaker Inc. haven't updated their web companion javascript to ensure compatibility with Mozilla.

My 2 cents: FM uses in IWP CSS technology much more, than JS. All browsers not sufficient with that technologies are out...

[Peter Kyme]

Unable said:

"Does anyone know if there is a workaround for this that doesn't involve going to custom web publishing?"

IWP = WYSIWYG,

IWP = WYSIWYG,

IWP = WYSIWYG ("anything I say three times is true", Alice).

If you are experiencing problems with IWP is it because your intuition has not allowed you to design your database(s) to take advantage of the WSYIWYG features of FMPro's IWP. Shame on you for being a bad designer (this is facetious and do not take it personally, please).

FWIW, FMI has a postiton paper which states in effect that they are a database solutions company and that they have done quite enough (thank you) in the field of the www. If you are turly energetic you can research their website for this statement.

Thanks for your feedback - however in this case the layouts are working fine - it's the actual IWP interface that is broken (Ie. the next record & previous record buttons for example). Since this (if I'm not mistaken) is built in to the IWP, it makes IWP a bit of a non-starter (unless there is some workaround for this).

I should explain, I would be glad to use CWP & CDML except that the idea here is that non-technical staff will be able to alter these pages/layouts without my intervention.

[Peter Kyme]

kenneth2k1 said:

Wouldn't ya know it, the manual has a section "About browser requirements." Read chapter 14 in the manual, particularly from 14-11 on.

There might be something here to give you some answers.

Thanks, but the manual just states that the browser must support CSS1 & JavaScript. I'm testing IWP using Mozilla 1.4 which was released days ago & definitely supports CSS1 & JavaScript. This is not some obscure browser produced in a bedroom, it's the 2nd biggest browser & the engine behind Netscape 7.

I can't believe it would take that much work on the developers part to patch the IWP plugin for Mozilla compatibility.

[Peter Kyme]

Ok, I've found a workaround. Solution is to disable the IWP interface and re-implement all the buttons in your IWP custom layout.

Incidentally, Mozilla renders the layouts perfectly, much better than IE5 on OS X.

[Unable]

"...the answer is in your abilities as a FMPro database developer..."

"Ok, I've found a workaround."

Congratulations. See, it was good advice.