AnsweredAssumed Answered

GetLayoutObjectAttribute( webviewer; "content" ) creates error (Windows only)

Question asked by arnoldkegebein on May 27, 2011
Latest reply on May 27, 2011 by philmodjunk


GetLayoutObjectAttribute( webviewer; "content" ) creates error (Windows only)


FileMaker Pro



Operating system version

WIndows XP

Description of the issue

Getting the content from a web viewer might create an error message "Encountered an improper argument" and 'breaks' the data viewer.

Steps to reproduce the problem

1. Create a new database (tables not required).
2. Add a web viewer to an empty layout.
3. Use the url "".
4. Name the web viewer object "wv".
7. Still in layout mode, open the data viewer.
8. Enter a new expression:
   GetLayoutObjectAttribut("wv"; "source")
9. Enter a new expression:
   GetLayoutObjectAttribut("wv"; "content")
10. Switch into browse mode.
11. Wait until the web page is loaded.
12. Click the first entry ("source") in the data viewer.
    -> No problem. It will show the expected result (""
13. Click on the second entry ("content").
    -> An error message "Encountered an improper argument." will pop up one or more times.
    -> Also, the expression will vanish from the data viewer. 14. Click on the first entry again.
    -> You cannot select the entry.
15. Doubleclick on the first entry.
    -> It will display the expression in the edit window. But when you close the window, the entry became invisible in the data viewer.
16. Close the data viewer and open it again.
    -> The two expressions are visible again, but clicking on them will repeat the error.

Expected result

After executing the expressing GetLayoutObjectAttribute("wv"; "content") I expect to get the content of the webpage currently displayed in the web viewer "wv".

Actual result

Error message: "Encountered an improper argument" and a broken data viewer.

Exact text of any error message(s) that appear

Encountered an improper argument.

Configuration information

Parallels Desktop 5 with Windows XP on Mac OS 10.6.7


No workaround found yet.