Some websites hijack the normal scrolling behavior (I assume they do it through Javascript, here is an example), which makes my trackpad become hypersensitive. Is there a way to disable this and use the browser default?
Just tried the link provided with Safari, Chrome and FireFox Dev Edition. Neither of them show this behavior.
Despite the question is clearly off-topic, why not just disable JS in our Browser?
Related
Note: This is the EXACT same question as this, but for FireFox.
Is there a way to "force" the tab to think that it is in or out of focus, like toggle pseudo classes in Developer Tools, but for the entire tab.
I am running FireFox on Windows 10. I could not find a way to do this using Developer Tools, and do not want to setup a whole testing framework just for such a simple thing.
Thank you for your time.
In the Firefox DevTools this is not possible (as of Firefox 67), so I've created an enhancement request to add this feature.
I'm integrating ckeditor instances inside alpaca forms. I've a strange behavior sometimes : Instead of
I have this :
This issue is not systematic and seems to be browser dependent, as I hardly have it in Safari, while it is more frequent on chrome.
Any clue about this ?
That happens usually when the browser uses a cached version of the toolbar icons.
Clear the cache of Chrome and verify with Firefox and IE.
I have C# MVC web app that has some textboxes that in IE9 you can enter in text, but you can't highlight via the mouse or via holding shift and the arrow keys.
I've looked around on the web and i've found other people experiencing this, with no solution.
One site i found claimed it was an issue with IE9 on pages that make multiple AJAX calls, which my site has but, removing AJAX really isn't a solution.
Is there a way via code or via settings in IE9 so that users can highlight text in a textbox? Or is this an outstanding bug in IE9?
Edit:
The website works perfectly fine in chrome
Turns out it was a rogue jquery statement that was
(.someClass).disableSelected()
that was disabling selection on every single textbox in my site. The kicker being that IE and Chrome handled it one way and Firefox a different way making it seem like a different bug
I had the same issue.
Select Tools on the IE bar / F12 developer tools. under the tab ( Document Mode IE9 standards ) check marked Alt+9. Closed the developer box. Closed IE9 opened it back up and everything worked as it should.
Hope this helps.
I have developer toolbar, any other tools I am missing ?
I am not doing any fancy graphics/html 5.
I have just been told I need to a support ie8; so want to know if I need to test in both, or just ie8.
Have used ms superpreview, but this is only good for static sites - I am developig a large data driven jsp website. and as far as I can see there is not any easy way to test on both ie6 ie8, without using a separate machine (albeit virtual).
edit
Will ietester remove my standard ie install (I want to keep developer toolbar). ietest will enable me to test under both, and then develop usign developer toolbar in whichever is my browser (ie6/ie8)
IE6 one of the most dumbest browser and biggest pain for both designer and developer. There is no guarantee that your site will work in both IE8 and IE6. As for checking you can use the IE Tester software which is free. Some even say that we should stop considering IE6 :)
You'll need to test in both. IE6 renders pages in a vastly different manner than IE7 or IE8.
Definitely not. If you need a page / site to work properly in IE6 then develop for that. More often than not a page that works in IE6 will work in everything else.
IE6 in particular is terrible with it's calculations regarding spacing, especially where padding is involved.
Test in both browsers on all systems possible.
Simple answer: NO.
you will need to test in all browsers you support as they all have differences to some degree.
IE6 is terrible at rendering css correctly.
you can use a tool called IETester to view your site in multiple version of IE although you wont have developer toolbar support. The other solution is to have different version on an windows image in a virtual machine.
The best way to develope a site is to develope it in a browser with the best support of css. (firefox, chrome, etc). Once you have done that then start adding browser specific fixes for browsers which do not display correctly.
Have a look at this article for how to setup your css file structure CSS
IE6 doesn't support HTML5 and CSS 3. In essence, your IE8 markups may not render well (in fact, many won't work at all) on IE6 (unless you do some CSS hack for IE).
If you want your system to work in both IE6 and IE8, test your system on both browser versions and make visual adjustments (CSS, HTML markup, etc.) accordingly.
Short answer: You cannot just code in IE8, you will need to test in IE6, too.
It's a very strange request to start coding only for those two browsers. Are you absolutely sure that's what you want? For example, what about IE7 or IE9? If you DO want to make your site as compatible as possible, in as many browsers as possible, you should make your site Standards Compliant (e.g. HTML 4 or XHTML).
Even if you don't, it's definitely where I'd start if I was going to focus on just IE6 and IE8. Unfortunately, IE6 will still likely give you trouble, but making your HTML/CSS standards compliant will make it easier a lot to ensure compatibility with IE8.
Tip to remember in IE6: If things aren't lining up exactly the way you imagine, it might be a carriage return in your HTML (yes, IE6 doesn't always ignore them *facepalm*).
Edit: Ah, corporate logic. I see.
I am having my first foray into website design and I am learning a lot. I am also now seeing why web developers are not a huge fan of developing for Internet Explorer. Nothing seems to work how I expect. However, since the website has to work cross-browser, I am spending time looking at it in Firefox, Chrome, and IE. Something that is very non-obvious to me, however, is how to tell where problems lie in the website.
For example, the layout of one of my pages forces a footer to the bottom of the page. It looks great in Chrome and Firefox, but there's something broken in IE that make the footer align to the right (and cause a horizontal scroll to appear). I have played around with the code, but nothing really is responding to how I want in IE (even though it does in other browsers).
Are there any tools that can help "debug" the problems on a web site so fixing it is more than just a trial-and-error approach? Thanks.
One of my favorites that works in all browsers is X-Ray. You simply stick the link on that page into a bookmark and it loads some external JavaScript on top of the page you're testing. It reveals a bunch of parameters about the DOM object you click on, as well as its hierarchy in the model.
As for your specific footer problem, I would look to a potential lack of clearing of floats and divs that are wider than their parent containers somewhere up the line.
There are frameworks like GWT, ext-js, YUI which hide a lot of the browser bugs from you. But today (near the end of 2009), there still isn't a good, realiable way to narrow down browser issues and to fix them.
PS: I'm collecting tools that help during debugging here: Which tools do you use to debug HTML/JS in your browser?
I assume you have checked that your code is valid, with
HTML validator, for example: W3C Markup Validation Service
CSS checker, for example: W3C CSS Validation Service
And, of course, you should have correct doctype in your html file. Without doctype, some browsers go to quirks mode to emulate bugs in old browsers.
A cross-browser JavaScript library, like jQuery and its UI components, can be very helpful in avoiding idiosyncrasies between browsers. Microsoft provides the IE Developer Toolbar, it's not quite as easy to use as Firebug, but can still be very helpful. A Just-In-Time debugger like MS Script Debugger or Visual Studio are also a time saver.
I like Firebug for Firefox
and IE8 has Developer Tools from the tools menu and IE Developer Toolbar for older versions.
Chrome has similar tools from the page menu.
All of which allow you to see elements on the page as they are rendered in their specific browsers, which I usually find very helpful in debugging browser specific problems.