I was building application based on jQueryMobile.
It worked correctly in all modern browsers except Internet Explorer. Application was displayed incorrectly and it was not functioning at all.
Solution to this problem was quite easy. I forgot to specify following line in the beginning of document:
<!DOCTYPE html>
Application started to work correctly also in IE after this small fix.
Just grab Google Chrome or Firefox 4 and watch this nice video clip 3 Dreams of Black.
Wonderful piece of computer art. 
You can find more info about technology behind the scene in following video:
Promised glory and unity of HTML5 API is falling apart. API keeps breaking with every new version of browser. That’s sad.
Firefox and Google Chrome implemented File API for manipulating with files. It contained very useful function slice.
Slice allowed you to read part of file content. This was quite handy when dealing with big files.
Poorly chosen name for API function caused split in browsers unity. Here is explanation:
This method was removed in Gecko 5.0 (Firefox 5.0) because its syntax differs from that of Array.slice() and String.slice(). Work is ongoing on standardizing its replacement, but for now you can use the mozSlice() method on Gecko-based browsers.
Nice.
Method was replaced by:
There is one important difference in the second parameter of function:
When you want to debug Flex app just start debugger in Flash Builder. It will launch browser, e.g. Firefox 4.
The problem is that when you stop at break point for too long, Firefox 4 will terminate Flash plugin. Default limit is 45 seconds.
This is useful behavior for normal web, but it’s not good for debugging.
Solution is quite easy.
Type URL: about:config
Enter filter: dom.ipc.plugins.timeoutSecs
Change value to -1
I found this solution at: support.mozilla.com
Happy debugging.
I was playing little bit with GLGE library.
Ermanno Balzi’s Standard Slide is now in 3D. You can test it here. Just wait few seconds after displaying stage. It will take some time to download model.
Requirements: browser with WebGL support. In these days it is Google Chrome or Firefox 4.
Here is sample screenshot:
Do you need more examples of WebGL in real world? Go to WebGL Earth.
In previous “POST” I mentioned solution how to dump client’s POST request at server side.
What about POST respose?
Start Firefox. Open Firebug Network monitor and…
… and it does not work properly for POST response.
Let’s try different solution. Start Opera. Open Dragonfly Network monitor and..
… and it does not work for POST response. Not implemented yet?
That is quite sad situation, but don’t worry there is simple solution.
There is plugin for Firefox known as HttpFox which works very well. (thanks to E. for link)
I would like to mention also one other tool known as Fideler2. It’s Windows application which allows you to track all HTTP communication from your computer.
Then there is another solution known as Wireshark. The only problem is that Wireshark does not work on Windows with some wireless interfaces.
Dobrá správa.
Inštalácia Flash Playeru už opäť funguje na Windows XP – CZ vo Firefoxe.
Vďaka Adobe za vyriešenie problému FP-5556.
Objavila sa chyba, kedy nie je možné nainštalovať Flash Player do Firefoxu na Windows/CZ.
Inštalácia prebieha z adresy http://get.adobe.com/cz/flashplayer.
Riešenie: zadajte priamo URL, ktoré neobsahuje CZ – http://get.adobe.com/flashplayer.
Chyba je reportovaná na bugs.adobe.com pod kódom FP-5556.
Narazil som na problém s Flex aplikáciou pod Linuxom. Načítavanie aplikácie sa pri štarte zasekne s chybou:
Error #2046: The loaded file did not have a valid signature.
Treba preveriť verziu Flash Playeru. Pravé ucho myši – About Flash Player. V mojom prípade bola inštalovaná: 10.1.51.95.
Po aktualizácii bol problém vyriešený.
Upozorňujem na to hlavne z toho dôvodu, že HTML template vygenerovaný z Flash Buildera typicky vyžaduje len verziu novšiu ako 10.1, takže uživateľ nie je vyzvaný, aby si zaktualizoval FP:
var swfVersionStr = "10.0.0";
Odporúčam zmeniť minimálnu požadovanú verziu na 10.1.82.
Typickým problémom pri štarte Firefoxu je jeho pomalší a pomalší štart.
Kde je problém? Nevedia vývojári vyvíjať?
Vývojári vyvíjajú dobre. Aspoň jadro prehliadača má porovnateľnú efektivitu ako u susedných prehliadačov. Problém prinášajú rôzne rozširujúce doplnky. Nie všetky sú úplne ideálne vytvorené. Naviac pri štarte Firefoxu sa postupne inicializujú. Stačí niekoľko chybných alokácii a než sa Firefox spustí, máte 200 MB pamäte preč.
Autorov modulov by som rád požiadal, aby si občas prečítali nejaké to odporúčanie. Tiež je vhodné požiadať o review kódu. Často stačí drobná úprava a modul má mnohonásobne menšiu pamäťovú stopu.
Ako zrýchliť štart Firefoxu z pohľadu používateľa? Skúste vypnúť moduly a sledujte, čo sa deje. Typicky jeden z modulov je nenásytný a stačí ho výpnúť.
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Jan | ||||||
| 1 | 2 | 3 | 4 | 5 | ||
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 | 29 | ||||
