Site Navigation

Friday, August 3, 2007

Site Feedback

Did you find a bug with this site? or want to provide some sort of feedback?

Drop me a line below, I'll be sure to check out what you have to say. If you want to submit a bug report on a browser, or framework / programming language, use the Submit a Bug form instead.

Cheers,
xyz

37 comments:

mmurph211 said...

I think I may have found another way around this bug --> http://webbugtrack.blogspot.com/2007/10/bug-235-createelement-is-broken-in-ie.html

I posted the solution I found on my web development blog here:
http://matts411.com/webdev/cre.....javascript

Let me know what you guys think.

Matt

Andy said...

http://webbugtrack.blogspot.com/2007/08/bug-242-setattribute-doesnt-always-work.html

I found a workaround which solves this.

var attr = element.getAttributeNode("class");
if (attr)
attr.value = "classname";
else
element.setAttribute("class", "classname");

Works for me in IE7.

Jared Mellentine said...

Re: Bug 126 - Using IE's attachEvent will break the 'this' object.

Steak said...

Regarding Bug 235 - setting name attribute in IE, an alternative workaround to set the name in the situation where you are not creating a new element, you can use the following:

try
{ // Try to set using IE compliant method
el.outerHTML = el.outerHTML.replace('<BUTTON', '<BUTTON name="foo"');
}
catch (err)
{ // Set for other browsers
el.setAttribute('name', 'foo');
}

Hope this helps as it doesn't seem to be a bug that is going away soon!

PS - seems that I can't submit with the greater than sign to open the button tag, so i've replaced it with the HTML Code - hope it displays correct.

Steak said...

Regarding Bug 235 - setting name attribute in IE, an alternative workaround to set the name in the situation where you are not creating a new element, you can use the following:

try
{ // Try to set using IE compliant method
el.outerHTML = el.outerHTML.replace('<BUTTON', '<BUTTON name="foo"');
}
catch (err)
{ // Set for other browsers
el.setAttribute('name', 'foo');
}

Hope this helps as it doesn't seem to be a bug that is going away soon!

Anonymous said...

Regarding Bug 210: No innerHTML support...

http://webbugtrack.blogspot.com/2007/12/bug-210-no-innerhtml-support-on-tables.html

Another workaround is to put the table inside a <div> and replace the entire table (the <div>'s innerHTML), rather than the table's innerHTML. Doing it this way, you can avoid having to use the DOM methods, but you have to make sure your table includes a <tbody> or the entire table will appear disabled in IE.

Anonymous said...

I submitted two bugs for review the other week; one concerned appendChild where for someElement.appendChild(someOtherElement)
in IE6 and IE7 the document of
someElement and someOtherElement
must the same. I've been able to reproduce this several times and have not found a workaround.

the other bug concerned loading a jsp page (say with an updated table) into a hidden panel and then using the DOM to access that table.
I reported that in IE6 I didn't seem to have access to that table
tho I did to fixed elements of the page.
I standalone version of IE6 that I'm using seems to have cookies turned off by default; when the jsp
page was loaded with the session id
attached to the url all was well.

you can reach me at
brian_whalley@yahoo.ca

thank you

Brent D. said...

Bug 119 for IE6 options that don't show the title tooltip

http://webbugtrack.blogspot.com/2008/06/bug-119-no-title-for-options-in-ie6.html

is actually only part of the problem. IE6 will not display the tooltip at all, even on the select element, so even if you hacked something to make it set a title on the select element it would still fail.

Brent

Anonymous said...

http://webbugtrack.blogspot.com/2008/05/bug-190-fieldsets-are-broken-in-ie8.html

This is fixed in the current partner builds so it'll be fine in beta 2.

Anonymous said...

for bug 404 the "cript is executing"

me thinks there is a typo there.

Christophing said...

IE6 Bug

Setting a background on a tBody element will make IE repeating the background in all the table cells nested to that element.

It's an unattended behavior and of course a bad rendering bug that doesn't occur on either Gecko or Webkit based browsers...

Anonymous said...

Element.setAttribute now works in ie 8, it worked for me

sergey k. said...

http://webbugtrack.blogspot.com/2007/08/bug-153-self-closing-script-tag-issues.html

Not only an IE bug but also it is in Firefox 3. It is handled correctly though by Opera 9, Safary 3 and Google Chrome.

Anonymous said...

On bug bug 193 - onchange does not fire properly on IE radio buttons and checkboxes:

The same problem exists for select items - at least, if the select box is a result of a XMLHTTPRequest. But if you pre-select one item like this ( i replaced the html braces with []:

[option selected]Something[/option]
[option]Something else[/option]

IE will fire the event, once you select something else. Kinda logically after you think about it. :D
So that's another workaround so to speak, or a related issue.

Nice collection of bugs you got there btw. - and even with solutions. Keep it up!

Anonymous said...

You are COOL MAN!!! You saved me a lot of time. Thanx, Guru!

Anonymous said...

The list of broken attributes and workarounds in bug 242 is really useful, thanks! I also have one addition for the list: the 'enctype' attribute (for forms) is also broken in IE; the workaround is to use 'encoding' instead.

jcartledge said...

re: Array.indexOf, the obvious workaround is something like:
if(!Array.prototype.indexOf) Array.prototype.indexOf = function(val){ ... }

Bart said...

Re: Issue: #181

There is a pseudo-workaround for this bug.

While you cannot do direct inheritance, you can "clone" the Array prototype and get a mostly functional length property.

Code:

// create your class
MyArray = function(){
// instantiates the "length" property so that it is non-enumerable
this.push.apply(this,[]);

// set the length property to 0, otherwise it is effectively undefined
this.length=0;

return this;
};
// create an explicit list of Array prototype properties to "steal" as you cannot use for/in loop to retrieve
var p=['push','concat'];

// manually copy the properties from the Array prototype to MyArray prototype
for(var x=0; x<p.length; x++){
MyArray.prototype[p[x]]=Array.prototype[p[x]];
}
var a=new MyArray();
a.push(1);
alert(a.length);// 1

// this fails, length property is only updated using the Array native functions
a[1]=2;
alert(a.length);// 1

end code

While this has some obvious drawbacks,it does get you a pseudo-subclass that works across all browsers.

Kit Grose said...

Re Issue #318

The sample doesn't crash Thursday's WebKit Nightly.

jimbojw said...

Regarding your post bug 109 - JavaScript prompt() in IE - How did this not get fixed in IE7?!:

Towards the end, it states that there are no known workarounds. I have just published one.

No, it's not another DHTML replacement - it's a real synchronous system dialog. Here's a link in case you're interested: How to fix window.prompt in Internet Explorer

Anonymous said...

The PHP bug with strpos() is really annoying.

http://webbugtrack.blogspot.com/2009/03/bug-271-strpos-function-in-php-returns.html

Its right there in the definition of the function. "int"
int strpos ( string $haystack , mixed $needle [, int $offset= 0 ] )

"int" as in: "This function WILL return an INT" - not a string, not a boolean or an object.

Java gets it right:

http://java.sun.com/javase/6/docs/api/java/lang/String.html#indexOf(java.lang.String,%20int)

I bet even ASP gets it right!

anyway I don't have a perfect solution but I look forward to whatever turns up here.

John B said...

regarding your bug http://webbugtrack.blogspot.com/2009/02/bug-519-ie8-inprivatewindows-media.html

# 519 with IE remembering content surfed in other browsers also has issues with Google Chrome. So it must be a Microsoft bug!

Kendal said...

Regarding http://webbugtrack.blogspot.com/2007/11/bug-184-catch-to-try-catch-finally-in.html

There's another workaround for the TRY/FINALLY bug that occurs in IE 7, 6, etc (but not in IE 8 when in IE 7 compat. mode, go figure). Wrap the TRY/FINALLY in another TRY/CATCH and re-throw the exception. The finally will run and the exception will cause an error (just like a TRY/FINALLY, except finally executes).

Anonymous said...

It seems fixed in 4.0.202.0.

martin said...

On page http://webbugtrack.blogspot.com/2008/08/browser-life-statuses.html
is missing reference to Opera 10 which was released on September 1, 2009

Cícero Feijó said...

Hi, if you add CSS style using this instruction:

function createStyleSheets(){
for(i=0;i<100;i++){
var css = document.createElement("link");
css.rel = "stylesheet";
css.type = "text/css";
css.href = "style.css";
css.id = "css_" + i;

document.getElementsByTagName('head')[0].appendChild(css);


var msg = 'Total Style Sheets = [' + i + '] of 100.';
document.getElementById('ssCount').innerHTML = msg;
}
}

Internet Explorer will accept the CSS requests, and the problem is solved. Or we have problem with this implementation too?

I see the DOM after this execution with Internet Explorer Toolbar and all nodes are inserted inside HEAD tag.

Thanks

Hery said...

good, i like it

sherryle said...

I think I have the same bug but I'm not positive, how do I find out for sure? My computer is running really strange and the curser is all over the place and there is other problems with the ad-ons and the ie not connecting to the internet when I'm on already, is this the same problem or am I on the wrong site? I been having this for some time and people tole me it's the ie8 and the updates and I don't know how to fix it. I'm not sure can you help?

Anonymous said...

http://webbugtrack.blogspot.com/2008/11/bug-471-font-weight600-stretches-text.html - doesn't work on Chrome either.

Jonas said...

Is bug 190 about this rendering problem?

IE8 screenshot:
http://bayimg.com/gaONiaacl

IE7 screenshot:
http://bayimg.com/GAONJAacL

Anonymous said...

for bug 263 it may have been fixed in preview 4 but it has been re-broken in preview 6.

IE iz teh #FAIL

Harold said...

The sample code you provided for bug 124 doesn't exhibit the bug.

http://webbugtrack.blogspot.com/2007/10/bug-124-setting-innerhtml-problem-no1.html

In the description you indicate that it will fail if the element is blank (which it does) but your sample code has a value and thus does not fail.

Anonymous said...

I've just stumbled upon this site and I must say it's awesome! A really neat bug database, that's cool! Thank you for creating it and good luck!

Jean-Luc Picard said...

Thank you so much for creating this site! This post was extremely helpful!

http://webbugtrack.blogspot.com/2009/02/bug-487-onclickonfocus-bugs-on-select.html

Jean-Luc Picard said...

Thank you so much for creating this site! This post was extremely helpful!

http://webbugtrack.blogspot.com/2009/02/bug-487-onclickonfocus-bugs-on-select.html

Jean-Luc Picard said...

Thank you so much for creating this site! This post was extremely helpful!

http://webbugtrack.blogspot.com/2009/02/bug-487-onclickonfocus-bugs-on-select.html

dedtri bimbang said...

ia good
Http://webbugttack.blogspot.com/2009/02/bug