Seaside form issue in Firefox and multiple open instances/windows

I've been running into a situation where when I have the same page
loaded in multiple browser windows.  The page contains a form where the
form fields will not be selectable (i.e. can't click to edit a text
field) in the window having the 'oldest' (i.e. first loaded) page.  My
best guess is that there's a page element that needs a unique name/id
that is shared between both windows as that's the only time I recall
seeing anything similar to this before (the issue I'm remembering had
nothing to do with Seaside though.)  This isn't happening all of the
time and I haven't yet been able to narrow it down to a reproducible
test case but was wondering if this rings a bell with anyone who might
have a solution or scenarios I should be looking out for?  I'm running
the latest Pharo-based Seaside with Firefox on Linux (haven't noticed
this issue under Chrome yet)

Thanks,
Phil

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

On Fri, Apr 24, 2015 at 11:04 PM, Phil (list) <[hidden email]> wrote:
> I've been running into a situation where when I have the same page
> loaded in multiple browser windows.  The page contains a form where the
> form fields will not be selectable (i.e. can't click to edit a text
> field) in the window having the 'oldest' (i.e. first loaded) page.

Can you inspect it with firebug or similar? Is it disabled in the DOM?

Cheers
Philippe
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

On Sun, 2015-04-26 at 19:27 +0200, Philippe Marschall wrote:
> On Fri, Apr 24, 2015 at 11:04 PM, Phil (list) <[hidden email]> wrote:
> > I've been running into a situation where when I have the same page
> > loaded in multiple browser windows.  The page contains a form where the
> > form fields will not be selectable (i.e. can't click to edit a text
> > field) in the window having the 'oldest' (i.e. first loaded) page.
>
> Can you inspect it with firebug or similar? Is it disabled in the DOM?
>

It doesn't appear to be.  I took a look at attributes on both the form
itself and a textarea on the form but didn't see any obvious differences
(the disabled property on the textarea is set to false on both the
working and non-working forms as well and various other properties I've
looked at on the form and textarea properties also match)

One additional detail I did notice is that none of the edit fields on
the entire page/tab are working when this occurs.  i.e. neither the
location text field nor the search text field are selectable either.  I
am able to select text and copy/paste it into another application but
can't type anything into any text fields in the tab.  If I close the tab
and re-open with a new session, this appears to temporarily work around
the issue.

> Cheers
> Philippe
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside