Alexey Ivanov
Top achievements
Rank 1
Rank 1
Alexey Ivanov
asked on 08 Apr 2011, 11:17 AM
I cannot submit a bug because I'm not a license holder, so I post here.
Steps:
1. Install Firefox 4
2. Install WebAii internal build 1607
3. Create file c:\1.html with the following contents:
<div id="div1"></div>
4. Run the following NUnit test fixture
Results:
ArtOfTest.WebAii.Exceptions.ExecuteCommandException : ExecuteCommand failed!
InError set by the client. Client Error:
mozCommandProcessor: TypeError: document.getElementsByTagName("div")[0] is undefined
Works fine with other browsers.
Steps:
1. Install Firefox 4
2. Install WebAii internal build 1607
3. Create file c:\1.html with the following contents:
<div id="div1"></div>
4. Run the following NUnit test fixture
[TestFixture]public class Fixture1 { [Test] public void Test1() { var m = new Manager(false); m.Start(); m.LaunchNewBrowser(BrowserType.FireFox); var b = m.ActiveBrowser; b.NavigateTo("c:/1.html"); var value = b.Find.ById<HtmlControl>("div1").ScrollTop; }}Results:
ArtOfTest.WebAii.Exceptions.ExecuteCommandException : ExecuteCommand failed!
InError set by the client. Client Error:
mozCommandProcessor: TypeError: document.getElementsByTagName("div")[0] is undefined
Works fine with other browsers.
5 Answers, 1 is accepted
0
Alexey Ivanov
Top achievements
Rank 1
Rank 1
answered on 08 Apr 2011, 11:40 AM
The issue is more generic.
It looks like JavaScript is executed in a wrong context:
ActiveBrowser.Actions.InvokeScript("document.documentElement.childNodes[10].tagName")
returns
"stringbundleset"
I don't have such tags in my document.
It looks like JavaScript is executed in a wrong context:
ActiveBrowser.Actions.InvokeScript("document.documentElement.childNodes[10].tagName")
returns
"stringbundleset"
I don't have such tags in my document.
0
Hello Alexey Ivanov,
Thank you for writing us. We have fixed JAvaScript problems with new FireFox4 and they will be available in the next internal build.
All the best,
Daniel Djambov
the Telerik team
Thank you for writing us. We have fixed JAvaScript problems with new FireFox4 and they will be available in the next internal build.
All the best,
Daniel Djambov
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
0
Alexey Ivanov
Top achievements
Rank 1
Rank 1
answered on 15 Apr 2011, 09:05 AM
Glad to hear it.
Waiting for the next internal build...
Waiting for the next internal build...
0
Hi Alexey,
We have prepared a new build that solves most of the FF4 problems. The only left issue we are aware of is JavaScript dialog handling we're still missing. They completely changed the dialogs in FF4.
Latest Build for FF4 Support
Please keep in mind the build is not thoroughly tested so we don't release it as internal build. If that's fine for you please let us know whether it solves the problems on your end too. Your feedback is highly appreciated!
Best wishes,
Konstantin Petkov
the Telerik team
We have prepared a new build that solves most of the FF4 problems. The only left issue we are aware of is JavaScript dialog handling we're still missing. They completely changed the dialogs in FF4.
Latest Build for FF4 Support
Please keep in mind the build is not thoroughly tested so we don't release it as internal build. If that's fine for you please let us know whether it solves the problems on your end too. Your feedback is highly appreciated!
Best wishes,
Konstantin Petkov
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Alexey Ivanov
Top achievements
Rank 1
Rank 1
answered on 18 Apr 2011, 01:25 PM
I confirm that this issue has been fixed in Build 1615