I want to run a twitter bootstrap code on tidesdk, does the web page display work like internet explorer, where bootstrap is not fully supported?
In other words what browser would tidesdk interpret the code most likely as. This is for making html and css code to look exactly like I want it to?
It will render similar to Google Chrome as it is a WebKit browser.
See: http://tidesdk.multipart.net/docs/user-dev/generated/#!/guide/getting_started
in conjunction with a WebKit client and a familiar and extensive API
TideSDK uses WebKit as underlying technology. You may find some difficulties as the webkit used is quite old. TideKit is the new technology and the future path for TideSDK users. here is the blog post about the comparison how TideKit would be better than TideSDK https://blog.tidekit.com/post/from-a-desktop-perspective-tidekit-for-tidesdk-developers
Related
I'm making an old website with HTML. I used the reset.css and I can see this perfectly on the web (http://www.ceachile.cl/revista/) with Chrome, Firefox and IE10, but my client can't see some elements properly. I don't know what else can I do to fix this table that is in a wrong place. Here's a folder with a lot of screenshots of the site in many browsers and OS.
Some snapshots of what the website looks like under various browsers can be found here
You have to check with elements of HTML and CSS each of the browsers support. Trident has historically been behind in implementing a lot of newer features. If you aim to support older browser, you have to look at their documentation and write code based on what they can handle.
Take a look at http://msdn.microsoft.com/en-us/library/bb250496(v=vs.85).aspx for ie7.
If you know your client's OS and browser version, you can use a service like www.browserstack.com to test your website in this environment and debug it with the usual developer tools.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am doing a project, which is a website and my plan is to write every html,css,javascript in notepad++, checking everything in google chrome all the time and when i am finished I will test from the start with IE (which is the most difficult) and the other known browsers and I will correct any issues (with the known methods).
My question is this: Which do you think is the best browser for this work? Which is most compatible with the others, so I won't have to do much work after finish my website on this and correct it for the others? In a few words, which browser is most cross borwser testing material?
Thank you in advance.
I would sudgest using Mozilla Firefox for playing with HTML / CSS.
One great thing it has is the FIREBUG add-on, which can be more tnah usefull while building your website. Check it out on https://addons.mozilla.org/en-US/firefox/addon/firebug/
You're doing it wrong - it's far easier to fix cross-browser issues as they occur, rather than have to tear through a complex project for a minor issue.
IE6 and IE7 can be safely discounted - as no-one uses them anymore. IE8 is the latest first-party browser for Windows XP and should be tested - it doesn't have any layout bugs, but doesn't support many CSS3 features like rounded-corners - so you might want a fallback stylesheet.
Firefox and Chrome are both very bug-free and have excellent CSS3 support, but have different styling defaults, so I strongly suggest using reset.css: http://meyerweb.com/eric/tools/css/reset/ as this irons out any potential issues.
I suggest Chrome.
1) It's the most popular browser.
2) It's got excellent developer tools.
3) It's webkit so you've also pretty much got Safari covered as well and webkit is also the foundation of most mobile browsers out there (Android/iOS).
IE 10 and Firefox are very similar to what Chrome will show as they're modern browsers. Then you're left with IE8, which I argue these days it's best not to worry about making it look perfect, just make it look good enough. Consider asking yourself what "support" means. I argue supporting an old browser means the site works, not that the experience is the same as Chrome.
Personally I would suggest Firefox - I find firebug invaluable (I've never been able to get along well with Chrome's dev tools) and it commands a reasonably high market share.
That said, if you find Chrome's dev tools good, it may be better to use Chrome (as has already been said, this covers you for Chrome + Safari, which is about 35-40% browser share)
Really it depends on personal preference, try both and see which you prefer.
As a web developer, you must be able to view your website/pages and easily debug it. Therefore, using Chrome is your best bet.
1. Built in Dev Tools.
2. Webkit. This is mostly supported on Safari as well.
3. A great browser to play around with. You can make all your fancy css3 stuff and test it out. If you like it, you can eventually add those to other browsers with javascript/jQuery.
4. Many many extentions. Though there just about the same amount of useful ones on Firefox, Chrome is IMO the best and most supported.
My list of Plugins:
- Chrome Sniffer - shows the framework a site is using... great for curiosity when browsing the net.
- Cloud Save - Lets you save files from websites to your cloud service of choice... great for web idea/resource browsing as well.
- Code Cola - Edit a section on your webpage directly for testing... like Chrome Dev tools but more direct.
- Eye Dropper - A must... lets you pick colors from webpages and find their various color codes.
- IE Tab - If you have windows, this is a great tool to have so you can view IE view inside Chrome.
- IPCV(Image Property Context Viewer) - See image values and such.
- Measureit - Find the dimensions of objects/classes/etc.
- Palette - Click on an image and it generates a palette from it.
- Resolution Test - A must have... check to see how your site displays on various browser dimensions.
- Session Manager - Save all your tabs for another session of Chrome.
- Web Developer - It does just about anything a Web Developer would need to know/test.
- WhatFont - Find out what font a website uses.
There is my qualities for Chrome... hope it is helpful!
Why pick one? If you include live.js and do your development with a locally running web server and then have your page open on all browsers you are testing against, the live.js code will automatically refresh the page every time you save a CSS, HTML or JavaScript file. You just have to add this line of JavaScript to the top of the page:
<script type="text/javascript" src="http://livejs.com/live.js"></script>
Also checkout IETester it lets you run multiple IE Rendering engines on a single PC (great way to test IE5, 6, 7, 8 and 9 (all on the same computer))
IE is the best for testing. here u can solve your design issue easily in compare of any other browser.
I recommend downloading Visual Web Developer 2010 Express (which is free), coding it there and checking you work with Chrome developer tools or Firefox firebug. In my opinion they are the best dev tools out there. Coding with Visual Web Developer express will be much easier as it has Intellisense built in and will save you lots of time. If you want to check your code for validation, use the W3C markup validator.
I want to develop an browser extension/add-on which keeps track of the url value in the address bar. The add-on could either be downloaded to local file system or it could be integrated within the browser.
Also, i'm curious to know how browser extensions like Toolyo are programmed. (It's a demo link of the Toolyo tool. Sorry, I didn't find a better example than this whic is much similar to my requirement). Can someone please throw light on the languages/methods used to develop extensions that can work in multiple browsers.
Sorry for a generic (and vague, as well) question. I would really appreciate any answers/suggestions.
The extension APIs for browsers with add-on functionality (Chrome, Firefox, etc.) are all very different and much of the browser-chrome-privileged code must be rewritten for the different browsers. User scripts, are a good alternative add-on architecture, but they only have the privilege level of an in-page script (except for GreaseMonkey in Firefox).
Greasemonkey is inbuild in Chrome
And also had support for Flock, Safari and Opera
And its also coming for IE soon.
So writing Greasemonkey script is also good rather then writing code per browser vendor.
I am working in creating a website and I want to check in multiple browsers for Browser Compatibility test automatically by using Automated Test Tool. Do you guys know if there is any software/tool where I can just give a link and it loads the page in multiple browsers?
I've used Browser Shots before and it's ok if you don't mind waiting for an hour or two.
I'd also recommend checking out some of the links on Delicious.
You're looking for litmus, from the people who brought you doctype, part of the League of Justice. 14-day passes to test your layouts in 24 browsers currently cost $39.
I'm a fan of XenoCode's "Spoon Browser Sandbox" myself.
You can use Selenium RC (Selenium 1) or Selenium 2 (WebDriver) for automated test. But You have to record the test using Selenium IDE on Firefox browser and writing some tests on it. Selenium supports FF, Chrome, IE, Safari and Opera.
If the website is publicly visible then there are web based services that you can use such as http://crossbrowsertesting.com/.
If your website is internal only, then you're going to struggle to find support I think. We tried to find one but all we found were services that require a publicly visible website - no good for testing pre-go-live.
Are you talking about a compatible design or compatible JS? Because AJAX functionality is difficult to test with the usual cross-browser tools.
For the latter, look at httpUnit, though I'm not sure it can simulate multiple browsers.
There's Microsoft Expression Web SuperPreview, but I haven't tried it so can't comment on if it's good or not.
Their opening quote makes me laugh though, mainly because of how sucky IE6 is:
About 7 years ago, the browser wars
were over. Internet Explorer had
become the de facto standard, and for
a while, there were very few
compatibility issues in web page
design.
Check it out though, might be worthwhile. Especially if you are a .NET developer, however it might be useful to web developers in general.
Adobe has BrowserLab. It requires an Adobe account (free) and gives you Firefox 2.0 - 3.5 (WinXP, OSX), IE 6-8 (WinXP), Safari 3-4 (OSX) and Chrome 3.0 (WinXP).
What, if any, considerations (HTML, CSS, JavaScript) should you take when designing for Google Chrome?
Chrome uses Webkit, the same engine as is used by Safari, OmniWeb, iCab and more. Just code everything based on the standards and verify in each browser.
I think first and foremost you should focus on using HTML and scripting that follows the standards.
After you have that running, file a bug report then make the browser-specific tweaks. If Chrome is worth a flip you shouldn't have to tweak things for it.
The same ones you'd take for Safari, as they share the same rendering engine (with a slight version mismatch).
I'm sure filing a bug report really helps with all those IE rendering issues!
Realistically, you need to test your application in each browser, no browser 100% follows the W3C standards so ultimately you can't rely on following that at all. You need to test everything you do in any browser you wish to support.
As has been mentioned, Google Chrome has the same rendering engine as Safari/iPhone/etc., WebKit which passes Acid3, so there should be minimal issues if you follow the standards. But don't rely on it. Google Chrome currently uses a slightly older version of WebKit than Safari. I'm sure they'll eventually be on the same version at some point, but unfortunately any new browser becomes just another browser to test in.
Are you designing specifically for Chrome, or do you want to make sure your pages work well with Chrome?
Assuming it's the latter, then just use the same design considerations you'd do for any browser. If applicable, keep in mind that many phones and video game consoles have web browsers now.
Chrome uses a new JavaScript engine, so you'll have to test your JavaScript using Chrome as well as Safari. The HTML and CSS may render pretty much the same, but they use different JavaScript engines.