Skip past navigation
On a mobile phone? Check out m.twitter.com!
Skip to navigation
Skip to sign in form

Hey there! ThorstenSuckow is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What are you doing? Join today to start receiving ThorstenSuckow's updates.

Already using Twitter
from your phone? Click here.

ThorstenSuckow

We've created an issue report for the #chrome #bug in #FF 3.5 : http://bit.ly/ZzuwJ Please vote!about 5 hours ago from conjoon
testcase for none-chrome bug #FF @arneblankerts : http://tinyurl.com/m22odaabout 5 hours ago from conjoon
@arneblankerts I'm going to whip up a testcase later on.about 6 hours ago from conjoon in reply to arneblankerts
@arneblankerts I'm trying to access a property of an element which FF identifies as a XULElement - thus throwing an error bc of chrome cont.about 6 hours ago from conjoon in reply to arneblankerts
@arneblankerts Maybe it's because of the none-chrome context? It happens when hovering Sbars and checking the target of the BrowserEvent.about 6 hours ago from conjoon in reply to arneblankerts
@arneblankerts The problem is that #FF thinks it's dealing with a XULElement and throws an error - see http://tinyurl.com/nnkjmuabout 6 hours ago from conjoon in reply to arneblankerts
@arneblankerts Already tried, doesn't work, #FF 3.5 interprets it as "object".about 6 hours ago from conjoon in reply to arneblankerts
Challenge: Check if node is XULElement in none chrome context, other than: Object.prototype.toString.call(el) === '[object XULElement]' #FFabout 7 hours ago from conjoon
@looriva Zumindest Grady Booch hat einen: http://bit.ly/vOaTKabout 8 hours ago from conjoon in reply to looriva
@corneliusweiss Yeah but that doesn't fix it - just like my workaround didn't, too. I think the "isXUL()" check is a pretty good solution.about 8 hours ago from conjoon in reply to corneliusweiss
@corneliusweiss Which kind of global error handler?about 8 hours ago from conjoon in reply to corneliusweiss
"Permission denied to access property 'dom' from a non-chrome context" - suggested fix for #ExtJs #FF 3.5 : http://tinyurl.com/nnkjmuabout 9 hours ago from conjoon
@InsideEXTJS Page fails with "Database error" :/11:12 AM Jul 16th from conjoon in reply to InsideEXTJS
@_Tinchen_ Mach ein Follower-Treffen und das Zeug ist im Nu weg.10:40 AM Jul 16th from conjoon in reply to _Tinchen_
@tdginnovations Early bird! Eagerly awaiting status updates of your new chapter. Log into the chat when you have the time.10:08 AM Jul 16th from conjoon
@reybango I know - but I'm pretty sure we'll send out a few invites ;)6:45 AM Jul 16th from conjoon in reply to reybango
@reybango Missed the opportunity to meet the crew this year - looking forward to shake hands with all of you on the next #ExtJS Con.6:39 AM Jul 16th from conjoon in reply to reybango
"Learning Ext JS" in the t100 progr. books on Amazon now and then. (via @VinlyFox) Congrats! You and Jay are the real evangelists of #ExtJS6:32 AM Jul 16th from conjoon
@reybango http://bit.ly/kZIWv Looks like a State Department needs some advise!5:10 AM Jul 16th from conjoon
@tdginnovations So did I - it's useful if you need to listen to dragstart/dragend events from a dragged component, such as Ext.Window3:17 PM Jul 15th from conjoon in reply to tdginnovations

Name Thorsten Suckow
Location Aachen, Germany
Web http://www.sitear...
Bio Ext JS & Ajax evangelist, maintainer of Ext.ux.Livegrid and conjoon

RSS feed of ThorstenSuckow's updates