Hiding MacOS Toolbar when in fullscreen - html

I was wondering if it is possible to hide the toolbar when in full screen using CSS. I've tried searching StackOverflow for some answer but sadly with no success.
Basically, go from this:
Too this:

No, you cannot affect the host application interface using CSS. There is a Javascript solution, however.
document.documentElement.webkitRequestFullScreen(); Be aware that you should also track keyboard actions like ESC, and provide a button for users to exit this experience as well.
Here's the documentation from Mozilla. Also according to the Can I Use database, Desktop Safari has only partial support and iOS Safari has NO support so how well this works will vary based on the browser.
I should point out that this isn't really the same as Kiosk mode. Kiosk mode can be used to block access from other applications/websites. This DOES NOT do that.

Related

In Nitrous.io, Is there a way to input stuff for the console in iOS?

The keyboard won't show up for console, and it is only for the editor. Is it possible there is some workaround about this? It is so close to fully support iOS!
Even better if nitrous.io guy can address this issue...
iOS is not officially supported so your mileage may vary when using an iPad, iPhone as well as other mobile devices.
Full iOS support is in our roadmap, I suggest following #nitrousio for product announcements.
Bluetooth keyboard works (in Chrome and Safari). Just tap inside the console area twice, then start typing.
Another option is to install a code editor (like Diet Coda) which provides an SSH console.

Is it possible to develop a web site for a touch based browser without using HTML5 or CSS3?

I'm developing the CSS file for the mobile version of the website my group are working on for our web design coursework, and I was wondering if it was possible to design a site for touch based browsers using the currently ratified specification of HTML and CSS, as the other member are doing for the desktop variant, or am I going to have to use the draft specification of the new language. I'm not intending to use anything too elaborate, I'm only attempting to allow the user to navigate the site with their finger, and the current implementation allows me to activate a dropdown menu on the desktop, but when I try to navigate on my Android handset, nothing happens.
The menu button gets illuminated in the way that all links in my browser do when they get pressed, but nothing happens. The research I've done since this revelation has led me to the conclusion that I'm going to have to experiment with the new spec, though since this is coursework, I'd rather stick with current standards than experimental drafts of new ones.
P.S. I'm only developing an informative site, not an application.
Yes, you can use older versions of HTML. iPhone, Palm OS, Android, and recent versions of the Blackberry OS all use Webkit, which is the same rendering engine that Chrome and Safari use.
In fact, the very first page on the World Wide Web will work just fine.
We'd need to see your code for your navigation bar to troubleshoot, but it's probably something along the lines of using a hover event to display the navigation (touchscreens can't have a hover event).
I can browse to any site on my iphone using the touchscreen. The language is not the problem. Most mobile browsers on smartphones can handle html(4)/css(2) fine. You should be more worried how to show the content so it will be easy to navigate on the site using a (small) touchscreen. Usability testing is your friend here. Browsing a website made for desktop can be very frustrating (not impossible) on a small touch screen.
Also the size of images and stuff shouldn't be to big. Since loading those can be a pain. At least the t-mobile(Netherlands) g3 network is slow, if available at all.
Note that the 'currently ratified' version of CSS is CSS1 (from 1996), CSS2.1 isn't yet a W3C Recommendation. So from that point of view the standards your other members are using for the desktop variants are not much more ratified than HTML5 and CSS3.
For sure do it! just ensure links are larger for fingers. Also allow the site to resize.
Most mobile sites are HTML1.0.
You would be silly using html5 + css3 unless you knew that it was only going to be used on an iphone eg. webapps.
And don't forget you can still use JavaScript!
Go For It!

What is the best service for cross-browser screen shots?

I have a website that I'd like to monitor for display problems in various browsers (mainly Internet Explorer.) I know that browsercam.com and broswershots.org provide this as a service. Could anyone recommend the best way/service to do this?
I have used browsershots.org. Internet Explorer is very populair and there are long waiting lists for IE versions. Most of the time you will not see your screenshot before your 30 minutes will expire.
You can try www.litmussapp.com. They have software which checks css.
oeps typo: it should be www.litmusapp.com
I like Adobe Browserlab, even though it's annoying that you have to create an Adobe ID to use it.
Theres also Microsoft SuperPreview and our new service, Browsera. One issue we faced with browsershots is that it scrolls the window to collect the screenshot, resulting in abberations if you have fixed positioned elements, or background images that don't scroll.
I like to use the Total Validator Pro Desktop Tool and do everything in one big shot. Validation, WCAG, Screen shots, etc. The online version lets you do one screenshot at a time.
As most options in this question are no longer around I would like to suggest the cross browser testing solution BrowseEmAll which can be used for testing (especially IE) desktop and mobile browsers.

Firebug-like debugger for Google Chrome

Is there anything like Firebug that you can use within Google Chrome?
Essential features I would like:
Inspect HTML source (select elements, delete them, etc.)
check CSS values (the built-in solution is weird, somehow)
There is a Firebug-like tool already built into Chrome. Just right click anywhere on a page and choose "Inspect element" from the menu. Chrome has a graphical tool for debugging (like in Firebug), so you can debug JavaScript. It also does CSS inspection well and can even change CSS rendering on the fly.
For more information, see https://developers.google.com/chrome-developer-tools/
Firebug Lite supports to inspect HTML elements, computed CSS style, and a lot more. Since it's pure JavaScript, it works in many different browsers. Just include the script in your source, or add the bookmarklet to your bookmark bar to include it on any page with a single click.
http://getfirebug.com/lite.html
Just adding some talking points as someone who uses Firebug / Chrome Inspector every day:
At the time of writing, there's only Google DOM inspector and no it doesn't have all the features of Firebug
Inspector is a 'lite' version of Firebug: The interface is not as good IMO, element inspection in both recent versions is now clunky, but Firebug is still better; I find myself trying to find the love for Chrome (since it's a better, faster browser experience), but for development work, it still just sucks for me.
Live preview / modification of DOM / CSS is still way better in Firebug; calculated CSS and box model view are better in Firebug;
Somehow it's just easier to read/use Firebug maybe because of the ease of navigating, manipulating/modifying the document in several key areas? Who knows. I'm used to the interface and I think Chrome Inspector is not as good although this is a subjective thing I admit.
The Cookies/Net tab are extremely useful to me in Firebug. Maybe Chrome Inspector has this now? Last time I checked it did not, because Chrome updates itself in the background without your intervention (gets your consent by default like all good overlords).
Last point: The day that Google Chrome gets a fully-featured Firebug is the day Firefox basically dies for developers because Firefox had 3 years to make Firefox's layout engine Gecko as fast as WebKit and they didn't. Sorry to put it so bluntly but it's the truth.
You see, now everyone wants to move away from Flash in lieu of jQuery motivated by mobile accessibility and interactivity (iPhone, iPad, Android) and JavaScript is 'suddenly' a big deal (that's sarcasm), so that ship has sailed, Firefox. And that makes me sad, as a Mozilla fanperson. Chrome is simply a better browser until Firefox upgrades their JavaScript engine.
F12
I love shortkeys
Try this, it's called Firebug Lite and apparently works with the beta version of Chrome.
You can also find it at:
https://chrome.google.com/extensions/
You can set this bookmarklet in your "Bookmarks Bar" in order to have Firebug lite always available in Chrome/Chromium browser (put this as the URL):
javascript:var firebug=document.createElement('script');firebug.setAttribute('src','http://getfirebug.com/releases/lite/1.2/firebug-lite-compressed.js');document.body.appendChild(firebug);(function(){if(window.firebug.version){firebug.init();}else{setTimeout(arguments.callee);}})();void(firebug);
Or try user scripts: http://dev.chromium.org/developers/design-documents/user-scripts
jQuerify is the perfect extension to embed jQuery into Chrome Console and is as simple as you can imagine. This extension also indicates if jQuery has been already embedded into a page.
This extension is used to embed jQuery into any page you want. It allows to use jQuery in the console shell (You can invoke Chrome console by Ctrl + Shift + j".).
To embed jQuery into the selected tab click on extension button.
The official Firebug Chrome extension or you can download and package the extension yourself.
https://getfirebug.com/releases/lite/chrome/
Well, it is possible to enable Greasemonkey scripts for Google Chrome so maybe there is a way to sort of install Firebug using this method? Firebug Lite would also work, but it's just not the same feeling as using the full featured one :(
willshouse.com/2009/05/29/install-greasemonkey-for-chrome-a-better-guide/
This doesn't answer your question but, in case you missed it, Chris Pederick's Web Developer is now available for Chrome: https://chrome.google.com/extensions/detail/bfbameneiokkgbdmiekhjnmfkcnldhhm.
Forget everything you all needs this browser independent inspector , dom updater
https://goggles.webmaker.org/en-US
just bookmark and go to any webpage and click that bookmark..
this is actually Mozilla project Goggles , amazing amazing amazing...
F12 (only on Linux and Windows)
OR
Ctrl ⇧ I
(⌥ ⌘ I if you're on Mac)
Please try Firebug Lite for Google Chrome
If you are using Chromium on Ubuntu using the nightly ppa, then you should have the chromium-browser-inspector

Does IE7 have a "developer mode" or plugin like Firefox/Chrome/Safari? [duplicate]

This question already has answers here:
Closed 11 years ago.
Possible Duplicate:
Debugging JavaScript in IE7
Firefox has Web Developer plugin and Firebug for troubleshooting html/css/javascript issues. Google Chrome and Safari have a very similar console and right-click options for "Inspect Element".
Does IE7 have anything similar for troubleshooting layout/html/css issues?
Yes - The Internet Explorer Developer Toolbar
Download details: Internet Explorer Developer Toolbar
You can also use Firebug Lite, wich works on IE, Opera and Safari.
It's a Javascript implementation that you can load with a simple bookmarklet.
As SO doesn't allow Javascript, here is the bookmarklet source code (just copy paste to your browser location bar (always make sure it's safe before executing random javascript (In any case check the first link)))
javascript:var%20firebug=document.createElement('script');firebug.setAttribute('src','http://getfirebug.com/releases/lite/1.2/firebug-lite-compressed.js');document.body.appendChild(firebug);(function(){if(window.firebug.version){firebug.init();}else{setTimeout(arguments.callee);}})();void(firebug);
Firebug Lite supports all basic commands of Firebug.
I have also used Debug Bar.
Check out the IE Developer toolboar.
Web Development Helper
Web Development Helper is a free browser extension for Internet Explorer that provides a set of tools and utilities for the Web developer, esp. Ajax and ASP.NET developers. The tool provides features such as a DOM inspector, an HTTP tracing tool, and script diagnostics and immediate window.
Web Development Helper works against IE6+, and requires the .NET Framework 2.0 or greater to be installed on the machine.
Once installed, the tool can be activated using the Tools | Web Development Helper command. You can also customize your browser's toolbar to add a button for this command to facilitate frequest use. Clicking on the menu command or browser button brings up the tool's console window and set of commands.
Page Features:
DOM inspector allows viewing all elements, selected elements, or elements matching an ID or CSS class, their attributes and styles.
Capturing a screen shot of the current page.
Viewing page information such as metadata, tags, and linked resources. .......
unfortunately it seems microsoft have discontinued it, the page for the toolbar now just says 'We are sorry, the page you requested cannot be found.'
I reckon because its built into 8 they have removed it for download, and cant be bothered with helping out us devs who are forced to make our projects work in their more archaic browsers :'(
Also before anyone says it, IE8 compatability mode != IE7
There's a toolbar you can get but it still doesn't match up to Firefox, especially for javascript debugging.
IE8 will be a huge improvement for development.
The following is specifically for IE7, other versions are probably similar.
Here is the new link to the developmment tools from microsoft.(as of 4-26-2011) IE Development Tools
Once installed, you will need to enable the toolbar.
To Enable, click on Tools | Manage Add-Ons | Enable or Disable Add-ons, to enable the addon.
To add the icon to the IE Toolbar, right click on the IE menu | Customize Command Bar | Add or Remove Commands. Add the "< (arrow) >" icon.
Hope that helps.
You can also use IE watch, which is like firebug, but you need to buy it. It is a 30 days trail version.
Actually, the best add-on for developers to IE would be Fiddler. It has a number of features that the other browsers possess.