Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

oauth responsiveness

ANSWERED

Am having a little trouble going through the auth window in an InAppBrowser, the page isn't responsive and the login form's content is a long way from view.  Can scroll down to it but am hoping a change can be made to the styles so this works well on iPhone / Android.

 

undefined

 

display: table on .outer is the most problematic thing here, something like this moves things in the right direction.

 

@media only screen and (max-width: 940px) {
  .outer { display:block }
}

What sort of turn around time do you have on bug fixes like this?

Best Answer
0 Votes
1 BEST ANSWER

Accepted Solutions

The OAuth 2.0 consent screen is responsive. 🙂

 

You can use the display=touch parameter when using OAuth 1.0a. See https://dev.fitbit.com/docs/oauth1/

 

 

View best answer in original post

Best Answer
0 Votes
4 REPLIES 4

The OAuth 2.0 consent screen is responsive. 🙂

 

You can use the display=touch parameter when using OAuth 1.0a. See https://dev.fitbit.com/docs/oauth1/

 

 

Best Answer
0 Votes

Thanks, will try this solution out.

 

Unfortunately one of the places this window is displayed is outside of our control, Validic.

Is there a reason you wouldn't want to include a simple responsive fix like I mentioned to get better experiences in those cases?

Best Answer
0 Votes

I appreciate the feedback and we might implement a responsive design for OAuth 1.0a, but we're prioritizing working on OAuth 2.0 at this time.

Best Answer
0 Votes

Understood, will look at upgrading to OAuth 2.0 but that will take some time.

Should be able to add display=touch to the page we have control over and will raise the issue with Validic also.

 

It sure would make my life easier if a style change like I posted could go out, doesn't need to be perfect but pulling the form into view would make it perfectly useable for my case, at the moment it's not useable at all.

Best Answer
0 Votes