So, I wanted to parse some page using Puppeteer, but I realised that it is very slow, many times slower than opening the same website in default Chrome browser.Why does it happen?
page.goto('https://rosreestr.ru/wps/portal/p/cc_present/ir_egrn')
I am trying to price out various azure services and when I add them to the calculator and make changes the estimate does not update.
I have tried this in Edge, IE, Chrome, Firefox (normal browsing and Private) and I get the same results.
I also ran CCleaner and removed all of the files for each browser.
The calculator did work a few days ago.
Any ideas?
I had the same problem. A solution that works for me is to open a new InPrivate window from the Edge browser. (A new private window from Firefox did not solve the problem).
Perhaps the problem is related to cookies? I have not tested after deleting all cookies. #jake, when you used CCleaner, was it set to delete cookies or just cached data and files?
(For what it is worth, in the Firefox developer console I see several warnings related to failed loading of JS scripts. I can't say if such a failure is the cause of the problem, but it looks like Microsoft needs to do better testing of the calculator page.)
we're trying to analyze some attack vectors on one of our MVC apps and we are considering writing some code to prevent users from accessing our site using a browser[version] that we consider to be too insecure.
For example, anything less than IE 7 is getting banned from our site.
Any browser [+version] that doesn't implement the HttpOnly cookie or has serious known holes/scripting issues would be on our watch list.
Without the obvious sarcastic comments about all versions of IE being totally insecure(!), which browsers and/or versions would you consider to be risky? IE tends to get all the bad press, but what about version 1 of Chrome or version 3 of Safari, etc.?
Honestly I still think most unsecure browser is IE. There is a lot of crashes and a lot of code execution bugs for IE. In last days of 2012, bluehole 0-day bug discovered being exploited in wild. But I don't remember last bug I've seen which successfully executes shellcode in Windows 7 with DEP and ASLR enabled. Those days almost passed for Firefox and Chrome. Specially chrome sandbox is really secure. I've seen only Vupen found a 0-day vulerability which executed code in Chrome like 1 year ago.
You can see list of vulnerabilities per year, per product and you'll see classification of bugs also.
http://www.cvedetails.com/product/3264/Mozilla-Firefox.html?vendor_id=452
Change product to Chrome, Internet Explorer and Safari.
Also IE is really vulnerable by third-party plugins, you can achieve code-execution easier on IE.
If you have more specific question, please ask.
SQL Server 2008 DB, report server, and IIS all on same Win XP machine inside firewall.
(Dev machine--production will be on a Win Server 2003 or 2008)
Test data is February, 21.5K records. Presumable other months will be similar.
Client and tester are Win XP SP3 with IE6. Long story, but can't change from IE6.
Report Server log shows that fetching, filtering, and rendering are all done within a little over one second.
If the parameter settings are such that the result set is 3,117 records, Visual Studio renders in ten seconds, IE6 in about a minute.
For a larger result set (not sure exactly, probably around eight thou), Viual Studio renders in fifteen seconds OR crashes. IE6 hangs forever.
Same parameters, Chrome thinks it's done in fifteen seconds. Doesn't display grid, but export to Excel works.
Safari, Opera, Firefox all fail to do authentication pass-through.
Not yet able to try IE7/8/9/... due to requirement to have IE6 on development machine. (Not that it matters, since client can't use it but I wanted to compare).
Unless a resolution can be found, I am going to have to give the client a pre-formatted URI for an Excel dump and have her do the filtering in Excel.
Looks like there is no answer. We're starting to free ourselves from IE6, but IE7 and IE8 have the same problem. And we're kind of stuck with them because we use Sharepoint.
The report works on FireFox, but FireFox fails to pass authentication through to Sharepoint.
Opera and Safari retrieve all the data, but don't display it. (When the busy curson goes away, the window is blank except the toolbar, but the "dump to Excel" icon works!)
So, the sort-of answer is
"The way to display huge amounts of data with SSRS is sometimes to not use SSRS"
I was starting to put it in another tool when the client decided other things were more important.
When you are working on a new website, what combinations of browsers and operating systems do you target, and at what priorities? Do you find targeting a few specific combinations (and ignoring the rest) better than trying to strive to make them all work as intended?
Common browsers:
Firefox (1.5, 2, 3)
Internet Explorer (6, 7, 8-beta)
Opera
Chrome
Common operating systems:
Windows (XP, Vista)
Mac OSX
Linux
Unix
Mainly I just target browsers as the sites I've built don't really depend on anything OS specific. As mentioned above, YAHOO's graded browser support guide is a good starting point on determining which browsers yous should/could support. And Yahoo's User Interface library (CSS+JavaScript) helps massively in achieving this.
But when developing sites I primarily do it on Firefox2 as it has the best web developing tools (firebug + wed developer toolkit). Then I also test my sites with Opera 9.5 as it's my browser of choice for browsing. I've previously lost all hope on supporting IE6 at any reasonable level so these days I just inform my users to upgrade to IE7 which is almost capable of displaying sites similarly to FF2/3+Chrome+Opera.
FF3 and Chrome are so new at the moment that I tend to ignore them, but I must say: They're friggin fast! My javascript/css heavy sites are noticeably faster with them.
I'm doing:
Firefox 2 and up
IE 7 and up
Konquorer or Safari (or maybe now Chrome)
Yahoo's graded browser support is a good guide:
It depends on your audience. If you are heavy on tech users, you may have 50% of you users as Firefox. If you have lots of mom and dads, you will probably have 75-80% of your users being IE 6 or 7. You probably need to get a alhpa/beta out with Google analytics so you can get a measure of your audience.
Where I work, we target
Firefox 2 and 3 on Windows
Firefox 2 and 3 on Mac
Safari on Windows and Mac
IE 6 and 7
We are not specifically targeting any Linux browsers, but if they work in the list above, there's a good chance they work everywhere. We are also testing against Google's Chrome browser on Windows now.
I just figured out this week that if you bend a little and figure out how to validate your HTML you're much more likely not to have to care about cross browser stuff.
Oh yeah, except Javascript.
I get it working in Firefox first, that's what the boss uses. Opera last, that's what Bob uses. Har Har, just kidding Bob.
But even so, you can never be safe because the minutia of browser incompatibility and the fact that 90% of the people you ask can't really tell you which browser they're using.
Can you click help and about? (Pause) No? Oh, that right you're using IE7
And even that old standby doesn't work anymore.
My advice is to lock down IE, like it's a terminal server, and try navigating your website. If you can click on everything and read everything then you're in the clear.
If you use sIFR and someone calls you telling you you're logo is upside down, it's time to prioritize and worry about compatibility again, otherwise IE and FF and you're good to go.
Target none. Test against many.
Where I work, we test the following (in this order of priority, based on data from google analytics), all on Windows:
IE 7
IE 6
Firefox 3
Firefox 2
Safari 3
We don't bother with Opera or older versions of browsers since the percentage of users is very small, however we do our best to code everything to standards, so there shouldn't be any big issues.
Of course, like Milhous said, it depends on your particular audience. YMMV.
The standard suite I'm used to is:
IE6 (win)
IE7 (win)
Firefox 1.5+ (win/mac)
Safari 2+ (win/mac)
Opera 9+ (win/mac)
Chrome (so far, if it clears Safari 3.0 on win, it seems to clear Chrome, too)
You could also generically claim support for IE6/7, Gecko, and WebKit... and it covers everything listed here but Opera, plus a few not listed. It's just a lot harder to test just the rendering engine and not the specific differences in browser versions and feel comfortable with the results.
I agree you should try and make it work in all, but if it is a new site I would seriously consider dropping support for IE6. From a development perspective it will save you hours of hair pulling if you don't need to support it.
You'll have to weigh this against your intended audience and whether you are willing to lose some customers that won't be willing (or able) to upgrade their browser.