File Select button doesn't work in latest version of Firefox

[Jark Monster]

Hi,

I'm using the latest Kendo (v2013.1.319), and I have hit a snag.  In Firefox ONLY, I cannot open the file browse window (accessed through the "Select..." button).

I am experiencing the same issue on the demos.
My version of Firefox is latest at v22.0.

I had another person test the demo on their machine in Firefox.  It worked at first when they were using v21.0, but when they updated to the latest Firefox version, the Select button stopped opening the file browse window.

Hopefully, this is an easy workaround/fix, but I did find that when tinkering around in Firebug, if I remove the k-upload-button class from the div element surrounding the input element, then it would revert to a Browse button and became clickable.

Here's my code, but it's virtually identical to that in the demo.  Please let me know if I can provide any more useful info.

@(Html.Kendo().Upload()
    .Name("ImageUpload")
    .Multiple(false)
    .Async(a => a
        .Save("UploadImage", "Home")
        .AutoUpload(false)
    )
    .Events(e =>
    {
        e.Error("UploadError");
        e.Success("GetImagePreviews");
    })
)

best,
-mark

[BigzampanoXXl]

You can try to update to the latest Kendo Q1 2013 SP1 release. It contains a lot of fixes. Maybe this bug is also fixed.

[Atanas Korchev]

Hello,

 The current official release of Firefox (at the time of this writing) is 21. In this version Kendo UI Upload seems to work as expected. I have recorded a short video of browsing our online demos: http://screencast.com/t/Sd7yVqpYWVG

Regards,
Atanas Korchev
Telerik

[Jark Monster]

BigzampanoXXl,

Unfortunately, upgrading to the latest build did not resolve the issue.  Thanks for the tip though!

Atanas,

I did check that v21 is the latest official version of Firefox, and I am aware that this version does indeed work.  Unfortunately, the default installation enrolls users in their Beta channel, which resulted in an automatic update to v22 about a week ago.  Though I know of course, Telerik has no control over that default setting, nor can I advise our hundreds of users to turn off automatic updates on Firefox.  I suppose I will have to wait for v22 to release (June 25th, I believe) and see if the issue still persists, and then revive this thread.

Out of curiosity, if you upgrade to v22, do you experience this issue?  At the very least it would demonstrate that it may not be the issue, but perhaps some setting on our development machines here at the office.  Any other tips you might have would be greatly appreciated!

Thanks for your help so far!

[Atanas Korchev]

Hello Mark,

 As far as we know the default update channel of Firefox is "release" (screenshot attached). We are not sure why think the default installation enrolls the users in the beta channel. Kendo UI doesn't support browsers in Beta stage. The technical requirements are available here.

Regards,
Atanas Korchev
Telerik

[Jark Monster]

Very strange.  I re-installed Firefox using the installer I had on my computer downloaded from Mozilla's site a couple months ago (v21), and upon re-install it put me in the Beta channel.

However, when I retrieved a fresh v21 install from Mozilla's site and re-installed again, I was placed in the Release channel.  *shrug*

I'll stick with v21 and release channel, but I am concerned that come June 25th and the release of v22 of Firefox that this image upload feature in my application will stop working after the automatic release update.  I was wondering about Telerik's turnaround time to achieve full compatibility with new releases of browsers.  Is it expected the day of the new browser's release, or will there be some down time? 

Understandably, this could not be a Telerik issue at all, but perhaps one within Firefox itself, but I just want to try and anticipate this issue and get any info I can on it now, should it affect our software in the near future.

Thanks for the help!

best,
-mark

[Atanas Korchev]

Hello,

 We usually fix browser issues on the same day they are reported. We then publish an internal build which incorporates the hotfix.

Regards,
Atanas Korchev
Telerik