I am using 1.44, maybe this was a bug that was fixed in a later version, but I am unable to upgrade due to all the fixes and customisation we have added ??

can a patch be applied to fix this issue ??

[UPDATE]

Jarry, thanks, that does NOT work.

in chrome (osx) the finder window that is opened to select a file still shows all files and not only files with the extension set in accepts.

UPDATE

OK, I just checked the generated html, and it appears that even though I have defined the 'accept' param in the javascript def, it does not get added to the <input type="file"> as an attribute, but it does get added to another input generated by the control ??

Code:

   $('#myfile').filebox({
      multiple: false,
      accept:'.xyz',
      onChange: function(nv,ov){
      ... more code
    });

html:

Code:

<input class="easyui-filebox filebox-f textbox-f" id="myfile" accept=".xyz" style="display: none;">
... more code

### Shouldn't this be the input that the accept attribute is attached to ???
<input type="file" class="textbox-value" id="filebox_file_id_6" name="">

If I then manually add the accept attr to the type=file it works as expected, I think this is a bug ?!

Code:

<input type="file" class="textbox-value" id="filebox_file_id_6" name="" accept=".xyz">

I can fix this issue with:

Code:

$('#myfile').next('span.filebox').find('input[type="file"]').attr('accept','.xyz');

Thanks, but I want to limit to extension type, not mime type i.e *.xyz

Is it possible, that when the filebox is clicked, the list of files that is displayed for selection can be restricted to a specific file extension ??

I know that I can check the filename AFTER selection, but I want to restrict the file extension type that the user can select.

Thanks

@jarry - this multibox control seems to work except for when using form.load() function.

I have created a setValue() function for this control, and for debugging purposes, I logged some text to the console when the setValue() function is called.

If I call this from the chrome javascript console, then the value is updated correctly and I see the text logged to the console, however when I use form.load() the text is not logged to the console and it looks like form.load() does not call setValue() on the control.

Any suggestions on what the cause / fix may be ?

You would call it just like you call any other standard control, only using the new control name.

Hi;

It's impossible for me to upgrade EUI due to the huge amount of customisation that's been added.

Can you let me have the code to add a 'cls' attribute to textbox in version 1.4.4 which was later added in V1.5.1 ?

Thanks

OK, then is it then possible to create a clone() function that will allow me to generically clone any control to a new control ?

This would be very useful :-)

Hi Jarry is it not possible to just do:

Code:

$.fn.multibox = Object.assign($.fn.combo);

I think it is somehow related to panel open / close, I get no errors when clicking a tab, but every control that uses panels seems to trigger an immediate vialoation.

This appears to be the jquery function that is triggering the error, but I have no idea why:

Code:

function () {
    var t,
    n,
    r = N.createElement('div');
    for (t in {
      submit: !0,
      change: !0,
      focusin: !0
    }) n = 'on' + t,
    (c[t + 'Bubbles'] = n in e) || (r.setAttribute(n, 't'), c[t + 'Bubbles'] = !1 === r.attributes[n].expando);
    r = null
  }();
  var V = /^(?:input|select|textarea)$/i,
  J = /^key/,
  Y = /^(?:mouse|pointer|contextmenu)|click/,
  G = /^(?:focusinfocus|focusoutblur)$/,
  Q = /^([^.]*)(?:\.(.+)|)$/;

specifically, this is the line that gets highlighted when the error occurs:

Code:

(c[t + 'Bubbles'] = n in e) || (r.setAttribute(n, 't'), c[t + 'Bubbles'] = !1 === r.attributes[n].expando);

[jquery.easyui.min.js]

I managed to solve this in my case on version 1.4.4:

jquery.easyui.min.js

Code:

//_51c.attr("src",window.ActiveXObject?"javascript:false":"about:blank");
_51c.attr("src","javascript:false");

But I am only allowing chrome / webkit browsers, no IE.

It is indeed caused by chrome cancelling requests on frames.

I am trying to implement CSP on my application, I have succeeded and are using sha256 digests on my inline scripts and the page now load without any error.

But as soon as I click on an element, such as a combobox, or open a panel I get a violation.

Any body else experienced / solved this problem while maintaining security ?

I believe this is the cause:

https://www.google.com/search?q=ajax+chrome+83+cancels+ajax&oq=ajax+chrome+83+cancels+ajax&aqs=chrome..69i57.286j0j4&sourceid=chrome&ie=UTF-8

Any solutions ?