nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Child Item

Drop-in Chooser on Windows Phone 8.1

Tyhrstan B.1

Hi,

On the previous dropbox forum I posted an issue regarding the Dropbox Chooser on Windows Phone.

I stated that when using desktop mode on IE (windows phone) the dropbox chooser works as expected, and only on Mobile mode it did'nt work.

I received the following answer on this topic:

Hi There,

I just tested and can't seem to get the chooser to work in windows phone 8, even with desktop mode enabled. (Though desktop mode does bypass our check). The trouble seems to be in how the windows phone handles popups. Whereas all other browsers correctly open a popup when asked to do so, windows phone seems to interpret our attempt to open a popup as a redirect. Since the user has been redirected away from the page they were on, we can't return the chosen file info to the page in the same context the user last saw that page. I believe the behavior is correct as is.

-Chris

The probable reason might be that I was using Windows Phone 8.1.

You were right about the fact that Windows Phone IE doesn't open a popup in a new window cause this disturbes the flow and every page runs in an isolated mode (so they can't interact). But the 'pop-up' can still interact with the 'parent' page.

I've created a similar construction where a pop-up is used to authenticate a user in linkedin and when the user returns to the 'returnurl' I call window.opener.{function} to invoke a function on the parent page.

And this works on Windows Phone 8.1

Find more posts tagged with

API

Abuse

Comments

Steve M.

Do you have a question? Or are you proposing a way to make the Chooser work on Windows Phone 8.1? (If so, please provide some code so we can see what you're talking about.)

Tyhrstan B.1

Hi,

Well, my proposel is that the Dropbox Chooser already works on Windows Phone 8.1, except the Dropbox.isBrowserSupported() function prevents it from working.

In visual studio I can start a IE debug session on Windows Phone, if I Then replace the Dropbox.isBrowserSupported() function by :

function() { return true; }

The dropbox file chooser works as expected.

So my proposel would be to finetune the isBrowserSupported function to enable Windows Phone 8.1,

useragents for IE11 on Windows Phone 8.1 can be found here https://msdn.microsoft.com/en-us/library/ie/hh869301(v=vs.85).aspx

Steve M.

Tyhrstan, we can't reproduce this behavior. I've created a simple page (http://wpchooser.site44.com/) that overrides isBrowserSupported as you did, and it doesn't seem to work on the Windows Phone 8.1 device I'm testing on.

Would you mind trying that same page to see if it works for you? If so, could you provide details about the device you're testing with?

Tyhrstan B.1

Hi Steve,

I've looked at the site.. and at first I couldn't reproduce it as well.

But it seems that the Alert() function isn't working. the screen freezes,

When debugging the page I stepped over the alert function and executed: $('#clickme').text('Worked: ' + files[0].link); This showed the selected file in de click button.

Steve M.

What device are you using?

Tyhrstan B.1

I'm using a Lumia 920, using Visual Studio I can start a debugging IE session on my phone.

Steve M.

Would you mind browsing to http://www.whatsmyua.com/ and copying the user agent? I'm trying to figure out why this would work on your device and not ours.

Tyhrstan B.1

Hi,

My useragent:

Mozilla/5.0 (Mobile; Windows Phone 8.1; Android 4.0; ARM; Trident/7.0; Touch; rv:11.0; IEMobile/11.0; NOKIA; Lumia 920) like iPhone OS 7_0_3 Mac OS X AppleWebKit/537 (KHTML, like Gecko) Mobile Safari/537

{
  "ua": "Mozilla/5.0 (Mobile; Windows Phone 8.1; Android 4.0; ARM; Trident/7.0; Touch; rv:11.0; IEMobile/11.0; NOKIA; Lumia 920) like iPhone OS 7_0_3 Mac OS X AppleWebKit/537 (KHTML, like Gecko) Mobile Safari/537",
  "browser": {
    "name": "IEMobile",
    "version": "11.0",
    "major": "11"
  },
  "engine": {
    "name": "Trident",
    "version": "7.0"
  },
  "os": {
    "name": "Windows Phone",
    "version": "8.1"
  },
  "device": {
    "model": "Lumia 920",
    "vendor": "Nokia",
    "type": "mobile"
  },
  "cpu": {}
}

Tyhrstan B.1

My Lumia 920 runs:

Windows Phone 8.1 Update

version: 8.10.14234.375

with the Lumia Denim update

Steve M.

It's possible the Lumia Denim update is the important difference. The page fails in the tests I've done, so we can't enable it for all Windows Phone 8.1 users. I think that for now we'll leave things as-is.

Tyhrstan B.1

I'm not sure if this is the case,

The emulator in Visual Studio runs regular Windows Phone 8.1 and I can produce similar results.

If you could change:

<button id="clickme">Click me</button>
    <script>
        Dropbox.isBrowserSupported = function() { return true; };
        $('#clickme').click(function (e) {
            e.preventDefault();
            Dropbox.choose({
                linkType: 'direct',
                success: function (files) {
                    alert('Worked: ' + files[0].link);
                }
            });
        });
    </script>

to:

<button id="clickme">Click me</button>
<br />
<span id="result"></span>
    <script>
        Dropbox.isBrowserSupported = function() { return true; };
        $('#clickme').click(function (e) {
            e.preventDefault();
            Dropbox.choose({
                linkType: 'direct',
                success: function (files) {
                    $('#result').text('Worked: ' + files[0].link);
                }
            });
        });
    </script>

I think it should work.

Steve M.

That change won't matter on my test device, since the Chooser "popup" (not really) never closes, so that code is never executed.

I was unable to get the phone emulator to connect to the internet on my Surface, so I gave up testing there and used a real device instead. I imagine the emulator uses the latest IE also, so your result doesn't surprise me. (If it works on your Nokia, I would expect it to work on the emulator too.)

Tyhrstan B.1

I understand you can't make changes if you can't reproduce this behaviour.

The emulator (Virtual Machine) in my Visual Studio doens't run the latest version, I haven't got the latest (Windows Phone 8.1 Update 1) emulators installed from https://dev.windows.com/en-us/develop/downloads, only the Windows Phone 8.1 version.

I hope future updates will make this possible.

Could you tell me wich phone model / OS version your using? Perhaps I can find the same phone and OS version to test my findings.

Steve M.

Okay, we actually managed to reproduce the behavior you're seeing. The alert was indeed the problem, though I don't understand how. (The alert on the background page seems to have blocked the Chooser page from actually closing?)

In any case, this works for us too on Windows Phone 8.1 Update 1. We're trying to track down a Windows Phone 8.1 without any updates to verify that it works on all versions of Windows Phone 8.1. If it does, we'll change the logic in the library to allow use on Windows Phone 8.1.

Tyhrstan B.1

Hi Steve,

Great that you've been able to reproduce the behaviour.

I believe what might be the reason is that the alert is initiated from the background page, while the background page is not visible.

To my understand the chooser works as following: when you select a file from the chooser the [success] function on background page is invoked and after this function completes the chooser page is 'closed'. probably an alert message can only be shown from and on the active page.

I'm looking forward to seeing the changes in library!

Steve M.

We managed to test this on a non-updated Windows Phone 8.1, and the Chooser works fine there too.

An update to the JS library should come out early next week, at which point the Chooser should just work by default on Windows Phone 8.1. Thanks much for pointing this out and hanging in there while we tested!

Tyhrstan B.1

Hi Steve,

That's great news! I'm already seeing the updated version.

I'm glad I could help out.