Browser Widget doesn't release focus to fields

[jacque]

It may be a glitch in the way LC auto-selects the first editable field when a card opens. (I wish we could turn that off.) Try adding this to an opencard handler on one of the affected cards:

on openCard
-- anything you may already have goes here
send "focus on nothing" to me in 1
end openCard

That will remove the field focus and when you then click into the field it should behave normally again. At least, that's the theory. Let us know.

[MaxV]

I have a similar same problem: if the browser read a page with a field like www.google.com and I start to type in it, I can't enter anything in other fields.
Look this example:

[montymay]

Thanks, Jacque, for your suggestion. I added your suggested line to the opencard handler, but it had no effect. I opened the card with the handler, clicked into a field, and typed text normally, then I left the card and returned to it, clicked in the same field or any other field on the card, typed, and no text appeared. I used to correct by toggling the browses/edit mode, but now I realize that clicking on any window outside the affected window, e.g., the desktop or the inactive LC menubar, "releases" the glitch. Then I can click into a field and enter text normally. I thought it might be my computer (Windows 10), or that the problem would go away when my app became a standalone, so I made it a standalone and ran it on a different computer (Windows 7), and got the same behavior and fix, i.e., click outside the window. MaxV has a similar problem, but it's surprising that my problem has not occurred to others. I hope that the cause can eventually be found, for no end user would use the app for long.

Monty May

[jacque]

Okay, then this sounds like a bug you should report.

[MaxV]

if it is this: http://quality.livecode.com/show_bug.cgi?id=19023 , it's an old bug.

[montymay]

Hello again,

Maybe I' don't understand the bug report, but it seems to me that the bug labeled 19023 and described in the link above may be the cause of my problem. I do my work on Windows and am developing for just the Windows platform. If the presence of the browser widget on the same card as fields is the cause, then it would seem that it would be a major problem for not a few LC developers (most platforms are still Windows), and yet it is little discussed on this forum and, as noted, it is an "old" bug, i.e., not a major problem. The bug report says it may depend of the URLs. A major part of my app is the use of the browser widget to display locally stored PDFs, so I can't avoid incompatible URLs. In my app users are requested to enter text related to the PDF. If LC cannot fix this bug and if it is the cause, I must decide whether to abandon this app. Or I could tell the users to click outside the window before typing in the field! I tried to login at LC Quality Control to inquire about progress but I have yet to get a reply in my email. I'll keep trying.

If this is causing the behavior in my app, could there be a "workaround" for this bug that I don't know about? Appreciate your comments.

Monty May

[montymay]

Hello LC forum,

My last post under the old subject heading having received no comment, I experimented and found that the title of an old thread can changed to a more informative one. Perhaps there is nothing to comment other than if my app is being affected by uncorrected bug no. 19023, there is nothing to do except wait for LC to fix it. I submitted my problem to LC Quality Control Center on July 26, but have received no response. Just wanted to make sure that all that can be done has been done.

Monty May