[webkit-dev] issue: accessing DOM elements directly, without using getElementById() from inside javascripts

[David Kilzer]

It's possible that the bug is in JSC, but since it works for *.html pages, it seems like it may be an issue with "enabling" this feature in XHTML pages.

https://bugs.webkit.org/show_bug.cgi?id=22211

Thanks again for filing this bug!

Dave



________________________________
From: "Deshpande, Raghavendra" <raghavendra.deshpande at philips.com>
To: David Kilzer <ddkilzer at webkit.org>
Sent: Wednesday, November 12, 2008 11:28:33 AM
Subject: RE: [webkit-dev] issue: accessing DOM elements directly, without   using getElementById() from inside javascripts


Hello Dave,
   
 I would like to share my opinion.  
As per my observation, it work fine in Chrome, but not in Safari. And the major difference between these two is, the JS core. 
 
So, Can this be a bug in JavascriptCore ?
 
Warm Regards,
Raghavendra Deshpande
 
________________________________
 From: David Kilzer [ddkilzer at webkit.org]
Sent: Thursday, November 13, 2008 12:56 AM
To: Deshpande, Raghavendra
Subject: Re: [webkit-dev] issue: accessing DOM elements directly, without using getElementById() from inside javascripts


Hi Raghavendra,

Thanks for filing the bug.  Please feel free to CC me on it.

I don't know what causes the issue (I'm not currently familiar with the code that may have the bug), so I don't know if it's a quick fix or not.  The fact that it works when you change the file suffix leads me to think that it could be a quick fix, though, once the buggy code is found.

Dave




________________________________
 From: "Deshpande, Raghavendra" <raghavendra.deshpande at philips.com>
To: David Kilzer <ddkilzer at webkit.org>
Sent: Wednesday, November 12, 2008 10:25:13 AM
Subject: RE: [webkit-dev] issue: accessing DOM elements directly, without using getElementById() from inside javascripts


Dave,
  
    I will file it as a bug. Its strange that, if you just rename my test page to .html ... All works fine. 
I am not able to understand this. Can you please enlighten me on this behavior.
 
And, Do you have any idea on a quick fix for this issue?.
 
Warm Regards,   
 
Raghavendra Deshpande
 
________________________________
 From: David Kilzer [ddkilzer at webkit.org]
Sent: Wednesday, November 12, 2008 11:11 PM
To: Deshpande, Raghavendra
Cc: webkit-dev at lists.webkit.org
Subject: Re: [webkit-dev] issue: accessing DOM elements directly, without using getElementById() from inside javascripts


Please file a bug using <https://bugs.webkit.org/enter_bug.cgi?product=WebKit> and attach your reduced test case.  Thanks!

Dave




________________________________
 From: "Deshpande, Raghavendra" <raghavendra.deshpande at philips.com>
To: "webkit-dev at lists.webkit.org" <webkit-dev at lists.webkit.org>
Sent: Wednesday, November 12, 2008 2:58:39 AM
Subject: [webkit-dev] issue: accessing DOM elements directly, without using getElementById() from inside javascripts


Hi All,
 
    In Gtk-Webkit browser,  we are facing issues with respect to accessing DOM elements directly, without using getElementById() from inside javascripts. We have many XHTML pages written already, without using getElementById() and all the pages are perfectly working fine in Opera. 
 
As “Chrome” is built using webkit, I tried testing the pages on ‘Chrome’. To my surprise, the same files worked fine in ‘Chrome’.
 
Then, I tried with Safari, (latest nightly updated), the behavior is same as Gtk-Webkit. It throws, “Can’t  find variable: DOM element name”
 
Have any of you faced such an issue?, Is there any fix for it?
As we can’t change the pages now, Is there any temporary hack?
 
Warm Regards,
Raghavendra
 
________________________________
 The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20081112/0e882cc0/attachment.html>