When opening dev tools, the device mode Icon is often not available.
In trying to determine why, it appears that it's use is now limited to a single tab in the browser. It used to work on as many as you liked.
It's extremely problematic,
as I often have several responsive pages that need comparison.
Anyone know why Google is limiting that function?
I used that an average of 8 hours a day for the past year and a half,
and suddenly it's unavailable for most of the tabs I have open.
does anyone have a work around?
Related
We have an application which displays a (complex) table of (~500) rows which can be edited via a modal dialog (PrimeFaces). Displaying the table (or doing any ajaxy things like changing some status on save buttons) takes much more time in IE9+ (5-6s) than in Chrome or Firefox (< 1s).
In the Internet Explorer's profiler, I see that most of the time is taken by the JQuery.attr() method which is called by PrimeFaces' updateFormStateInput().
I really don't know how to go deeper in identifying the cause of this problem or if this bad performance is considered normal for IE.
Switching to Chrome/Firefox is not an option as our users have other applications that only work with IE (sharepoint).
So, is there anything I can do to solve/identify the problem? (Except removing each component one by one and see if this improves performances.)
I usually have three chrome windows open. To easily distinguish my work chrome from the personal chrome window, I would like to set a theme to one window, and another theme to other windows.
I figure out how to change the theme globally, wondering whether its possible to it per window.
Use different profiles. You can do this in chrome by clicking the Proflile icon in the top-right of any window. It'll ask you to log in with your Google account but you're able to make a local account with any name.
I use one for personal (personal google account), one for work (work google account), and a third with no google account for risky or other website browsing (which has more aggressive blocking rules)
I do have in mind 2 options, since I really want to easily identify them.
You can add name to your window, not so noticeable since only shows on hover on mac.
You can also group all the tabs in that window, to give it a bit of a different color
which you can see here. blue and red. Bit noticeable.
for windows users, can you try this options, it might be better there.
I did some research into this issue, and it seems the only way to do this is to open different browsers e.g - firefox for presonal stuff, chrome for work etc...
will be happy to see a better solotion though...
i was working with Screen and some Qwebkit based browser. I do thumbnails of specific entrys of a webpage via Achnor. That worked fine till some days.
The issue is that a lot of webbrowsers (including my crawler) aren't able to Jump to a specific Anchor of a post entry. This issue occours only on this specific Website by Blizzard Entertainment.
I took a look into the webpage several times with firebug but i can't see the reason for the Bug. I hope that someone is able to tell me whats wrong with it.
http://eu.battle.net/hearthstone/de/forum/topic/14899382319?page=4#69
I've found lots of information about measuring load time for pages and quite a bit about profiling FPS performance of interactive applications, but this is something slightly different than that.
Say I have a chart rendered in SVG and every click I make causes the chart to render slightly differently. I want to get a sense of the complete time elapsed between the click and the point in time that the pixels on the screen actually change. Is there a way to do this?
Measuring the Javascript time is straight forward but that doesn't take into consideration any of the time the browser spends doing any layout, flow, paint, etc.
I know that Chrome timeline view shows a ton of good information about this, which is great for digging into issues but not so great for taking measurements because the tool itself affects performance and, more importantly, it's Chrome only. I was hoping there was a browser independent technique that might work. Something akin to how the Navigation Performance API works for page load times.
you may consider using capturing hdmi capturing hardware (just google for it) or a high speed camera to create a video, which could be analyzed offline.
http://www.webpagetest.org/ supports capturing using software only, but I guess it would be too slow for what you want to measure.
The question may be a bit theoretical (did I mean rhetorical?) or fuzzy, but here it is anyway.
I'm planning to build a web page where content will be added through Ajax requests and displayed using tabs and panes. The initial view has just one tab and shows a list of links. Clicking on a link opens a new tab/pane. The user can navigate through the tabs and close them, just like in a web browser.
I could build a UI able to display an unlimited number of tabs, but that implies adding DOM content to as many -- and possibly a lot of -- panes. More likely, I'll set a limit to how many tabs can be open simultaneously. But what should that limit be? What rule would you follow? What's your experience in how much content a DOM document can hold without impact on performance?
There is no way to answer your question. I, for example, have Chrome and Firefox running side by side right now. All browsers together need 9.85GB of shared memory (so some of that RAM is shared between all browsers; I have only 8GB of RAM and about 2GB is actually in use).
There is no JavaScript API to tell when memory gets tight; the only indication is that the machine is starting to swap or that the browser is crashing.
So you have the following solutions:
Limit the user to something that is too small. Good for you, bad for power users like me.
Set the limit too big. Bad for you, since users will start complaining how your stupid site makes their browser crash but good for me.
Instead of setting a limit, clear the panes which are not visible. Save the state of the pane somewhere (server, local storage) and restore it when the user opens it. Quite some effort but it would solve your problem.