I am trying to migrate my 4.9 DHTML application to 5.0. When i am doing that i am getting an error
ReferenceError: EVENT_OBJECT_FOCUS is not defined
[Break On This Error]
this.sendAAEvent(0,EVENT_OBJECT_FOCUS)
And in the line i am seeing this set of code. From the class name it looks like it is a radiobutton class.
$lzc$class_baselistitem,["tagname","radiobutton","children",[{attrs:{$CSSDescriptor:{},$attributeDescriptor:{types:LzNode.mergeAttributeTypes(lz.ClassAttributeTypes["accessible"],{EVENT_OBJECT_FOCUS:"number",EVENT_OBJECT_NAMECHANGE:"number",EVENT_OBJECT_SELECTION:"number",EVENT_OBJECT_STATECHANGE:"number"})},$classrootdepth:1,$delegates:["onselected","$mb5",null,"ontext","$mb6",null],$mb5:function($0){
if(!this.isinited){
return
};if(this.selected){
this.sendAAEvent(0,EVENT_OBJECT_FOCUS)
};this.sendAAEvent(0,EVENT_OBJECT_STATECHANGE,true)
},$mb6:function($0){
this.sendAAEvent(0,EVENT_OBJECT_NAMECHANGE)
},EVENT_OBJECT_FOCUS:32773,EVENT_OBJECT_NAMECHANGE:32780,EVENT_OBJECT_SELECTION:32774,EVENT_OBJECT_STATECHANGE:32778,name:"accessible",updateFocus:function($0){
if($0){
this.sendAAEvent(0,EVENT_OBJECT_SELECTION);this.sendAAEvent(0,EVENT_OBJECT_FOCUS)
};this.sendAAEvent(0,EVENT_OBJECT_STATECHANGE,true)
}},"class":LzState}
This is happening because of the radio.lzx .has anyone come across an issue like this.
I am currently using FF 16.0 windows xp sp 3 and Openlaszlo 5.0.x revision 19830
I would try with a different Firefox version or Firefox on a different OS. I have the feeling that it might be a Firefox bug in one specific version of Firefox.
The only mention of the EVENT_OBJECT_FOCUS can be found in OpenLaszlo's JIRA issue LPP-7594 Jaws Accessibility support needed for Radioboxes. It doesn't seem that any bug has been filed.
Related
I am trying to upgrade my KendoReportViewer JS file. I was using 'telerikReportViewer-10.0.16.min.js' before. Now I have upgraded it to 'telerikReportViewer-12.2.18.min.js'. After upgrading, the parameters section of reports is not showing.
I am using KendoReportDesigner for building reports. CAn anyone guide me where I am wrong.
Thanks
The report viewer and report server have to be identical in version or at least close. I have asked Telerik support about this before.
I have an app I have been working on that was running fine.
I upgraded to the latest Xamarin with mac support and now I get an error when I try to use HttpUtility.ParseQueryString.
I have an App.config file and it is telling me that it can't parse it, but this happens when trying to call ParseQueryString. How are those 2 related?
I thought I had found the problem because my app also has a ServiceReferences.ClientConfig file for http client settings. I copied my App.config section to the ServiceReferences.ClientConfig file and that fixed it until I went to show my fellow dev the new error.
The new error was saying something about Path.Combine path1 being null.
I looked up that error and found a reference to a page talking about MacSupport in xamarin here: https://searchcode.com/codesearch/view/8556026/
I don't know if they are related, but that is the closest I found to the stack trace I was seeing.
Can anyone tell me what changed in Mono 4.8 for Mac in Xamarin that would cause an issue with HttpUtility.ParseQueryString and how to solve it?
System.Configuration is a common point of pain during mono upgrades, as it's behavior sometimes subtly (or not so subtly) changes.
You'll need to post a much larger chunk of information here for anyone to be able to help you.
Or you could post on the XM Forms or file a bug if you believe this is a bug, as those are a more appropriate place for such reports.
While using Magento 1.9 (I think that's not very important) I've got following errors in IE9:
SCRIPT438: Object doesn't support property or method 'observe'
validation.js, line 98 character 35
This exception points to an Event.observe call, and there are more exceptions like that.
The prototype version is 1.7.0 and it's loading as first script (by the script src) in header element. All the errors occurs in scripts which should be loaded/initialized after the prototype.js.
I'm debugging it for a few hours without results. The problem does not occur in other browsers.
Do you know how to fix that?
Try upgrading to the latest version of Prototype, and see if that solves the issue. There was a lot of work done in IE compatibility during 1.7.3.
http://coldfire.riaforge.org/
I can't get the current version (1.9.207.249) to work in with Firefox 14.0.1 with Firebug 1.10.2.
I assume it is broken because the plugin has not been updated for the release of Firebug 1.10.
Has anyone got it working with these settings?
A new version of ColdFire was released that should work with Firefox 15/Firebug 1.10.
https://github.com/nmische/ColdFire/downloads
Based on this I will assume it's still alive. Perhaps try the Chrome version?
http://www.raymondcamden.com/index.cfm/2012/8/24/First-release-of-ColdFire-for-Chrome
We have a plugin that we use to enable printing and saving from our
app. We instantiate it using tag with all needed attributes,
and then call Save() or Print() method on the document.embeds[0]
object.
This used to work perfectly on Firefox 3.5 and earlier, but it no
longer works in Firefox 3.6. In 3.6, document.embeds[0].Save is null,
that is our custom methods are not defined on this object.
Any idea why this happens, and what has changed in Firefox 3.6 that
causes it? Any idea on how to debug it and find the cause? And most
important, any idea of a workaround that will allow us to access this
methods?
Thanks,
splintor
Got an answer in mozilla.dev.tech.plugins forum - Firefox 3.6 removes support for XPCOM. We will need to change our plugin according to one of the options suggested in the answer.