Advice on accessing page simultaneously with multiple browsers
-
When attempting to access, say, http://ip.address/ui/some-page with more than one browser, odd behavior occurs (as might be expected with two browsers running angular js...). Over time, the second browser simply shows a blank div, effectively, of the custom page being viewed by the first browser (although it, of course, loads any other pages not with the same route).
Curious if you have any on using multiple browsers to view the same page. One might be separate 'duplicate' pages, assuming they all have their own application scope. Thanks for your thoughts.
-
@bullitbd said in Advice on accessing page simultaneously with multiple browsers:
When attempting to access, say, http://ip.address/ui/some-page with more than one browser, odd behavior occurs (as might be expected with two browsers running angular js...).
Odd behavior should not occur, nor would I expect it.
@bullitbd said in Advice on accessing page simultaneously with multiple browsers:
Over time, the second browser simply shows a blank div, effectively, of the custom page being viewed by the first browser
Simply viewing a page in one browser should not affect another browser viewing a same page. If you have inputs/controls on the page and you interact with them then perhaps you might see a change in the second browser if you have coded your page to behave this way. Please elaborate on what you mean by a blank div, a screen shot of the two browser windows and the markup from the custom page would be useful. As also would the version numbers of your software and the output of the browser console and ma.log. Please see https://help.infiniteautomation.com/reporting-bugs/
@bullitbd said in Advice on accessing page simultaneously with multiple browsers:
Curious if you have any on using multiple browsers to view the same page. One might be separate 'duplicate' pages, assuming they all have their own application scope.
I'm sorry I can't understand this, please check what you wrote. If you are talking about AngularJS scopes, every browser has separate memory and will have its own AngularJS $rootScope, they do not interact at all.
-
will do, Jared. can I privately post markup to you?
-
@bullitbd said in Advice on accessing page simultaneously with multiple browsers:
will do, Jared. can I privately post markup to you?
Yes, put the markup somewhere (Google Drive, https://pastebin.com/, https://gist.github.com/ etc) and send me the link via chat (on my profile page)
-
Hi, @Jared-Wiltshire - well, I was away from the "first" browser when I made that observation. It turns out that I am no unable to render any custom page in a direct link, edit pages preview or dashboard designer. All other function of the UI work normally. I've sent you one page's markup, but appears to be something else.
-
@jared-wiltshire said in Advice on accessing page simultaneously with multiple browsers:
a screen shot of the two browser windows and the markup from the custom page would be useful. As also would the version numbers of your software and the output of the browser console and ma.log. Please see https://help.infiniteautomation.com/reporting-bugs/
-
Oh, sorry - thought I'd done that. The ma-log and code links are in your chat. Running 3.5.6 on ES.
Interestingly, I found the culprit. I had recently changed a filter to the wrong syntax in an angular expression per a previous thread (see: @phildunlap said in ma-point-value: number formatting, and that threw the following (note in the ma-log):
Error: [$parse:syntax] Syntax Error: Token '(' is an unexpected token at column 28 of the expression [tankTemp.value/256 | number(1)]
When I fixed that error, all pages rendered again. Not sure why it affected rendering of all pages - so just fyi. Thanks.
-
@bullitbd said in Advice on accessing page simultaneously with multiple browsers:
When I fixed that error, all pages rendered again. Not sure why it affected rendering of all pages
It wouldn't unless you visit the broken page then navigate to another. It always pays to check your pages with the dev tools open to check for error messages in the console.
-
point taken!