‘too much time spent in unload handler’ – chrome error
Bumped into this error while invoking a webcal link (and staying on the same page). Apparently clicking the link starts a sequence that eventually fires onbeforeload, which in its turn causes the error.
Reports of this bug first popped in search near the end of February January and probably related to a recent chrome build (Chrome Version : 4.0.249.89, Official Build 38071). After letting the issue for few days, I did some extra searching today and came up with a tweet by @rvdavid:Held up by a “Too much time spent in unload handler.” error on #chromium. in trying to find solutions, All I find “unconfirmed” #bug reports. Replying to the tweet led me to a possible solution by the Chrome team. As far as I understand we may see the solution already merged into one of the next official releases. Will update.
Clearing an input of type=’file’
For obvious reasons, one cannot clear an input of type ‘file’ (in fact, the ‘value’ cannot be changed at all). Previous attempts to achieve this using setAttribute or direct access to the ‘value’ property has failed.
Our guys @ the UI team has found a useful workaround:
-
-
function resetUploadControl(control)
-
{
-
var parent = control.parentNode;
-
parent.removeChild(control);
-
-
var tempForm = document.createElement("form");
-
tempForm.appendChild(control);
-
tempForm.reset();
-
tempForm.removeChild(control);
-
tempForm = null;
-
-
parent.appendChild(control);
-
}
-
First, grab the elements’ parent, remove the control from it and append it to a temporary form. Input elements of type file can only be cleared by resetting the form they are part of, thus the temp form.
After resetting (and achieving our empty-valued input goal), re-append the control to its original parent and destroy the temp form. Mission accomplished! :)
Credit goes to Ori Roniger & Vadim Kononov
No commentsGoogle Apps stops IE6 support
Just got this by mail:
Dear Google Apps admin,
In order to continue to improve our products and deliver more sophisticated features and performance, we are harnessing some of the latest improvements in web browser technology. This includes faster JavaScript processing and new standards like HTML5. As a result, over the course of 2010, we will be phasing out support for Microsoft Internet Explorer 6.0 as well as other older browsers that are not supported by their own manufacturers.
We plan to begin phasing out support of these older browsers on the Google Docs suite and the Google Sites editor on March 1, 2010. After that point, certain functionality within these applications may have higher latency and may not work correctly in these older browsers. Later in 2010, we will start to phase out support for these browsers for Google Mail and Google Calendar.
Google Apps will continue to support Internet Explorer 7.0 and above, Firefox 3.0 and above, Google Chrome 4.0 and above, and Safari 3.0 and above.
Starting this week, users on these older browsers will see a message in Google Docs and the Google Sites editor explaining this change and asking them to upgrade their browser. We will also alert you again closer to March 1 to remind you of this change.
In 2009, the Google Apps team delivered more than 100 improvements to enhance your product experience. We are aiming to beat that in 2010 and continue to deliver the best and most innovative collaboration products for businesses.
Thank you for your continued support!
Sincerely,
The Google Apps team
I really hope this makes a difference and the IE6 abundance by a giant will eventually lead to the disappearance of this archaic and web-holding-back browser.
No commentsSteaming hot, straight from the oven – bLog-On
Just aired, Log-On’s job recruitment blog, didn’t know blogger is customizable at all… :)
http://b.log-on.com
Proud to be part of the team
It was just published that Clarizen has secured $8M in financing from leading VCs.
I joined Clarizen about 5 months ago, working for the UI/UX team.
My kid is a genius! :)
Omer will be 9 mothes this week :)
No commentsXMarks for chrome alpha 0.4.19
I’m a heavy user of XMarks as I use 3 different browsers, each one for it’s purpose (IE for testing at work when we are developing for mainly IE, FF for general dev and Chrome for fast Internet :)).
XMarks has now entered the alpha stage for the Chrome plug-in. I tested it on Chrome 4.0.206.1 and it works great so far.
ASP.NET bugs(!!) on official Zune HD site
Just visited the new Zune HD official web site, really wanted to look around.
Look what I got when I clicked “Personalize Zune HD”:
ASP.NET bug, Zune HD official website
Same goes to the “Buy” link…. Come on, please, some QA before depolying.
The error:
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Could not load type ‘ITSP.Zune.Customize’.
No commentsWrong image in article. mistake or a saying?
In an article discussing the rise of apartments pricing in Israel during the latest financial crisis, an image of a cemetery was added with the writing “The big drop in interest rates caused a big rise in the demand for apartments”. A cynical approach or a careless editor?
Google translated version of the image
