We have a print functionality on our application which we implement through JavaScript window.print where in we print those pages which have records to be displayed. Some of these pages have pagination which have records greater than 20.
The functinality works fine in almost all browers except IE 7, in which either the print popup does not open when the page has pagination or if it opens an empty page is printed.
Any pointers to deal with such a problem?
If I had to take a guess based on what I can see, it is more then likely not the window.print() function at all. To print we usually would use conditional style-sheets to format the page for print #media print but this is not supported by IE7, however a conditional IE style-sheet with an media="print" attribute can force it.
The reason I say this is because IE is a dinosaur now, it does not play nice when it comes to re-rendering for something like printing, so a conditional style-sheet is critical to get proper functionality.
Though considering that IE is so outdated and that even things like jQuery is starting to remove support, I would not be to worried and just stick with the more modern browsers witch will save you a lot more time in the long run.
this link shows another post similar to this one.
Support of media queries, IE 7 is not even listed!
Related
I am working on an web application in MCV asp.net that needs to work in IE. Loading the application with data for some customers we get the "The page can not displayed" using IE10 and IE11.
More details are
It works in Firefox.
The error is only there for large pages = larger DOM
An exampel of a large page is a body of 4.6MB measured by Fiddler
For small pages there are no problems
The error page apears instantly when loading a customer
We have tried the following, but with no luck:
Removing stepwise elements from a big page and at some point it will start working, since it just removing sets of the same elements, nothing is being removed that could couse the problem - maybe its something with the size of the http-response?
Changed some IE settings
Stripping away all Jquery and CSS, to see if it was some DOM traversal issues
Tjekking the http-response to look for any bugs - non found
Google around seams that IE will show this page in some situations, but not found anything to fix this problem, where the application works on some pages but not on others.
Any suggestions?
The answer to why it does not work in IE is that you can not have more then about 200 AntiForgeryTokens, above that will make IE not load the page.
The quick solution: reduce the number of AntiForgeryTokens, we could do it by not having a delete form per element.
Ive made a simple project with html and jquery. It works great in all browsers except for safari on ipads. Since apple doesnt have a windows version of safari i cannot check if the error is explicitly for ipad but i think so.
The problem is the photoboxes wich get their width from the jquery, they dont appear at all on the ipad. Chromes developer tools device mode shows everything correctly and i have css queries that take care of smaller screens so its only the ipad thats the problem. I havent found any way to do a web debug on the ipad either. Its hard to give a code example due to i dont really know what the error is but i have a live demo you can check out. For you on ipads, its supposed to be photos before the winter background.
http://www.mj-bygg.se/ipad/default.aspx
I am also getting the same error on desktop Chrome on the first load. If I refresh, then the pictures load fine but on first visit to the link I only get the footer image (trees.)
On the first load, none of your jQuery heights/widths are being applied. No errors in the console and if I rerun the function it works as it should (without reloading the page.)
I suggest either pushing the script further down the page or using $(window).load(function() {}
instead of
$(document).ready(function() {}
That is the only thing I can assume is wrong if it fails first time but works with the page being cached.
Good day,
I have a problem with IE and iframes.
So I have a huge application with legacy code, designed in early 2000. iFrames are used everywhere.
When something big is loaded inside the iframe, there is no display in browser throbber. So the loading icon starts spinning only when the main page is loaded, not iframes, so its impossible to say if anything is happening at all.
The users complain, that IE10+ gives them this problem, earlier versions worked. For me IE9 also has this issue.
Unfortunately, it is impossible to use JS on every page and manually add the 'loading please wait' icon or message, there are more than 100 pages with more then one iframe on each.
Chrome works fine, but nothing except IE can be used.
Could you please recommend solution for this trouble?
We did an application using rails(2.3.4), ruby(1.8.2), MySQL, JavaScript, jQuery. This is handling minimum 6000 records. We showing those records detail in table. In the beginning Mozilla taking 2m to load the whole page. We did the cache, eager loading, indexes. Now Mozilla taking 25s to load the whole page. But IE-7 taking 1m30s to load the page.
We don't know why IE-7 taking too much of time.
Any one can help us to detect the running time in IE-7 and tell your guidelines to improve performance in IE-7.
Any add-on is available in IE7 to see the AJAX request time taken as like Firebug add on.
Use partial loading. Don't try to load the 6000 records at once, load them in smaller segments, when needed. Even 5 second loading is too long, not to mention the 25 seconds or 1m 30s.
Oh and yeah, IE 7's JS engine just sucks.
From Table Rendering - IE Blog:
When Internet Explorer encounters a table it measures all the content
of the table before rendering so that it knows what the widths of the
columns are to render the content correctly. On the other hand Firefox
uses a different algorithm in that it renders the table contents
progressively before it has all been passed.
You can improve performance by setting the CSS rule table-layout: fixed. The renderer will then calculate the layout based on the first row of the table.
IE7 is slow, there's no real way of getting around that basic fact.
I'm going to answer your second question (about debugging tools for IE7) because I don't think I can give any useful advice on your main point about actually speeding up IE7.
Any add-on is available in IE7 to see the AJAX request time taken as like Firebug add on.
The first thing to try is IE8 or IE9. These browsers have a Developer Tools window (accessible via F12, just like Firebug). It isn't as good as Firebug, but it does do quite a bit, and it is a useful debugging tool. It also has a feature which allows you to switch the browser into IE7-compatibility mode. The idea is that you can test IE7 from the relative comforts of IE8 or IE9.
The down side is that it isn't actually IE7. It's just a pretend ID7, and not a particularly good one at that. It may or may not replicate the speed issues you're having with IE7, and it certainly has known bugs and quirks of its own which don't appear either in a real IE7 or in IE8 in normal mode.
But all that said, it might be good enough for you to run some tests and get some answers.
A second suggestion might be to try Firebug Lite. This is a cut-down version of Firebug which runs as a bookmarklet in any browser (but generally IE). It doesn't have all the features of the full version of Firebug, because there's only so much you can do without writing a browser plug-in, but it does do a surprising amount. If nothing else, it does give you the console functions, which can be a life saver for debugging.
I hope that helps.
Is there a way to reduce or filter the number of scripts shown in script debugger? With Chrome it just shows the file containing the scripts instead of every single script block.
Also, when I set debug points on an inline script and go through the code the page reloads and selects the first script in the drop down. I then have to reset all my break points.
Overall Opera seems to be pretty cool, just need to find a way to work around these few annoyances.
I don't think there's any way around these at the moment. My experience with Dragonfly is pretty similar... Overall it's great but there's a couple of small annoyances :)
You could try filing a ticket to get it fixed.
There's a filter in the Scripts dropdown now, should make it easier to get where you want to go. On breakpoints, I'm not sure what you mean. They shouldn't disappear unless you close Dragonfly or change the debug context. You can always see all Breakpoints and navigate directly to them from the Breakpoints panel on the left.
If not, then yes, please file a bug.