I have 2 update panels each with a refresh button to reload the contents.
When i click on the refresh button it takes 10 seconds to reload the contents, meanwhile before its contents are fully loaded, if user presses the refresh button 2, it stops the execution of first panel and starts execution of second panel.
Is it possible to execute 2 update panels in parellel?
Parallel asynchronous Ajax requests using jQuery
How many concurrent AJAX (XmlHttpRequest) requests are allowed in popular browsers?
Related
I am making a chrome extension that fetched JSON data from CoinMarketCap.com API and currently I have it running in the background script. I'm not 100% sure what the purpose of the page is really. I was wondering if I could simply fetch the data from the popup script after I click a button within my popup?
Each button represents a different coin. I basically want to get the price of a chosen coin and display it on whatever page the user is on when they double click the coin in a text article. Eventually I want to make it so you can double click any coin and have it show a live price conversion while you're on the web-page.
The point of a background page is to be always available (running if persistent: true, woken up / recreated for registered events if persistent: false).
A popup's lifetime is determined by its visibility. The moment the user clicks away and closes it, the page is closed (as if the tab with it was closed), so it can no longer process any events and its state is lost.
As long as:
The data you need fetched is to be received/processed while the popup is open
Any state you need to persist between popups being shown can be stored in chrome.storage
Then you don't need the background page to do the fetching. Popup page has the same level of access to Chrome APIs.
However, consider this scenario: suppose you want the data to be ready as soon as popup is opened (at least, you want it to be fresher than "since last time"). You may want to do periodic updates even while the popup is closed to refresh the data. You can only do that reliably with a background page (and, say, chrome.alarms API). Then you can cache the latest available data in chrome.storage and use that in the popup.
Background pages have their uses as some code that can run periodically regardless of user actions, and to be able to always react to events.
According to Changes to Cross-Origin Requests in Chrome Extension Content Scripts now you have to do your fetches in Background Script. Not in Content Script.
I have a screen with multiple tabs around 10 to 12. I am loading data in each tab component separately in OnInit. When the request is in pending state chrome network tab, the UI freezes. Not able to click the already loaded tabs. Is this the browser behavior or Angular?
I would like to understand whether asynchronous actions in browser affects the rendering performance.
I am clicking on a Menu Item which takes the user to a different page on the application. After clicking menu item , script waits for few seconds or more than a minute sometimes before moving ahead to the next step. There are no wait/delays etc after click and have verified from logs that it keeps waiting after clicking menu item and does not move ahead to the next line. This is the description of menuitem (using chrome sampler)
id="SummaryMenuItem" href="../AppsView/page.aspx?ViewID=cc1d569c-6f26-4a4f-bc64-86fb1fdbb236&Layout=MarketData&Theme=Default" onclick="addToNav('../AppsView/page.aspx?ViewID=cc1d569c-6f26-4a4f-bc64-86fb1fdbb236&Layout=MarketData&
My chrome sampler script
wait.until(conditions.presenceOfElementLocated(pkg.By.xpath('//div[#id=\'navMenuSubs\']//*[#id=\'SummaryMenuItem\']')))
var subMenu = WDS.browser.findElement(pkg.By.xpath('//div[#id=\'navMenuSubs\']//*[#id=\'SummaryMenuItem\']'))
subMenu.click();
Can anyone suggest why script keeps on waiting
Thanks
Usually clicks are not recorded in the jmeter but the request initiated by the click (click event-->request to the server) is getting recorded. If co-relation is not done properly then it may not proceed further.
If there is no request send due to click then nothing will be recorded.
Hope this helps.
I'm using the Network tab in Chrome Dev Tools to profile how my page is loading.
It shows a blue line after the DOM is loaded, then a red line after the page finishes completely loading (all the ads, etc).
However, there are apparently AJAX requests that continue to happen periodically in the background and then network tab keeps timing these -- the result is that the granularity and detail of the initial page load gets lost as the scale keeps being increased.
The DOM usually loads within 1 second and the page is usually done loading in under 8 seconds, and there are dozens of resources to closely examine within these first few seconds, but the network tab tracks events that happen 1 minute and 3 minutes and 8 minutes out, etc. which results in 99% of the horizontal space being dedicated to tracking things I don't care about and 99% of the things I care about being squished into about 1 horizontal pixel.
I would like the network tab to stop timing after it reaches the red line.
There is a button in the upper right corner with the tooltip Record Network Log. If this button is red, then recording will continue. To stop the recording, press this button and toggle it to gray. Just wait until you see the red line indicating that the page is done loading, then hit the button to stop the recording of network events.
I am forced to use HTML::Mason for the dynamically generated web page. Unfortunately, the page depends on some long running computation. I need to display progress to user somehow. Is it possible to make Mason not to wait until the page is fully generated?
Having had a similar problem (though I was using Template Toolkit as the front end), the solution I used was to show the user a "query is in progress" page. This had a link that the user could click to check for results; if the query had finished, the results came up, and if not, another "progress" page was loaded. The page automatically refreshed after a certain amount of time so the user could just sit and wait if they preferred.
You could write some javascript that polls the server and dynamically loads the result into the page, rather than having the page reloading every x seconds.