Closed Bug 265073 Opened 20 years ago Closed 1 year ago

Filemaker Web Sharing only suppports IE, Safari and Chrome

Categories

(Web Compatibility :: Site Reports, defect, P5)

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: paul.carr, Unassigned)

References

()

Details

(Keywords: webcompat:contact-ready, Whiteboard: [country-all] [app] [contactready])

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; rv:1.7.3) Gecko/20040913 Firefox/0.10
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; rv:1.7.3) Gecko/20040913 Firefox/0.10

If you enable "Instant Web Sharing" on Filemaker 7, you get a page that warns
Mac user to use only Safari and IE, and Wintel users to use IE only.

Reproducible: Always
Steps to Reproduce:
1.Enable Instant WEb Publishing on Filemaker database
2.attempt to access via Firefox or Mozilla
3.

Actual Results:  
Warning message that IWP is optimized for IE and Safari.  In fact, performs
shabbily with Mozilla/Firefox.

Expected Results:  
Worked the same for Mozillas as for Safari
*** Bug 283186 has been marked as a duplicate of this bug. ***
*** Bug 264531 has been marked as a duplicate of this bug. ***
Since this has two dupes, I'm going to confirm it.

Do we have any contacts over at Filemaker?

It would also be nice to have a testcase so we know what to tell them. I'd be willing to bet that they're doing some bad sniffing.
URL: n/a
Status: UNCONFIRMED → NEW
Ever confirmed: true
According to their documentation
http://www.filemaker.com/support/technologies/webdirect.html

> Supported browsers include Safari, Chrome and Internet Explorer.

And in https://fmhelp.filemaker.com/docs/13/en/fm13_webdirect_guide.pdf

Windows: Internet Explorer 10
         Internet Explorer 11
         Chrome 27.x
OS X:    Safari 6.1.x
         Safari 7.x
         Chrome 27.x
Assignee: english-us → nobody
Component: English US → Desktop
Whiteboard: [country-all] [app]
Summary: Filemaker Web Sharing only suppports IE and Safari → Filemaker Web Sharing only suppports IE, Safari and Chrome
I guess we can't test this and just have to contact them - right?
Whiteboard: [country-all] [app] → [country-all] [app] [contactready]
A quick search of the community reveals some discussions:
https://community.filemaker.com/search.jspa?q=firefox

https://community.filemaker.com/message/199077 - some talk about relevance of Firefox
https://community.filemaker.com/message/508747 - someone suggests "Firefox does not implement HTML 5 the same way as the supported browsers"

Disturbing because the website claims the product uses web standards.
Reaching out by their email contact form: http://help.filemaker.com/app/ask
Assignee: nobody → astevenson
Status: NEW → ASSIGNED
Whiteboard: [country-all] [app] [contactready] → [country-all] [app] [sitewait]
Got a response:
"Thank you for contacting FileMaker Customer Support. I have forwarded your email to the appropriate team member on your behalf."
I haven't received a response and I don't expect to. Switching back to contactready for now, if someone else wants to try contacting.
Assignee: astevenson → nobody
Status: ASSIGNED → NEW
Whiteboard: [country-all] [app] [sitewait] → [country-all] [app] [contactready]
We used Filemaker and Firefox in a closed group for years and never had any issues.
After the update to v57 Quantum, I encountered a nasty bug and reported it to Filemaker:

https://community.filemaker.com/thread/180744
https://youtu.be/6gW_8_1lVHI
 
Short answer from Filemaker:
"FileMaker's WebDirect is not tested as supported on FireFox. While some functions may work as expected, you could run into any number of issues."
OK, so if they officially don't support us, I don't expect us to gain much traction here (which is sad :(), given the attitude hasn't changed in 14 years.

Thanks for reporting the issue to them, burned.
Priority: -- → P5
Product: Tech Evangelism → Web Compatibility

See bug 1547409. Moving webcompat whiteboard tags to keywords.

Severity: normal → S3

The page redirects to claris.com now. I could not find any documentation regarding the supported browser. Given the update, I will close this issue. If the reporter or anyone else could test the issue on the newly developed page and give us feedback on the issue, we will gladly reopen the issue.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.