Scroll of method content does not work in Safari and old Chrome and Firefox

[tuler]

When you open a method documentation, and it's too long, the scrolling does not work.

[meeque]

Hello Everyone! We (me and some colleagues) are experiencing the same issue. Any progress on that?

We tried to investigate, but we weren't able to pin it down exactly. Let me share our findings:

It's likely a pure CSS bug in app.min.css -- Safari and older Chrome/FF only render some CSS3 styles with an appropriate compatibility prefix. It mainly seems to concern styles related to display:flex, but maybe others, too. E.g. instead of:

 display: inline-flex;

We might need this (-ms- put in for good measure):

display: -webkit-inline-flex;
display: -ms-inline-flexbox;
display: inline-flex;

We tried to fix these problems manually (in our local copy of the dist) but we eventually gave up -- too messy:-\ I'm aware that it's preferable to adjust the sources of the Grunt-build. In particular a more generous configuration of the autoprefixer would be helpful. See configuration here (currently line 62): https://github.com/mulesoft/api-console/blob/master/Gruntfile.js

We did not try to fiddle with it yet, since we're hoping for an upstream solution;-) While the situation may improve for newer version of Firefox and Chrome, imho Safari users will remain affected by the problem -- it seems to to be Apple's policy to only accept prefixed versions of CSS3 properties for the time being. So maybe a special autoprefixer-rule for Safari might be helpful?

Thanks for your support!

[dmartinezg]

Hi @meeque, thanks for the headsup.

A team of ours is working on a new and redesigned console, so most of our work is focused on this https://github.com/mulesoft/api-console/tree/features/v2

If you would still like to keep using v1, you can help us by providing a patch for v1.

First you would need to I submit a Contributors Agreement for me to be able to pull your PRs in.

[meeque]

Thanks for the reply! Is there a schedule for the release of v2 yet? If it's released any time soon we might consider swithing to it...

I see in the Gruntfile of v2 that you are not using autoprefixer anymore? And that you switched from less to sass? So a solution for v2 might look slightly different. Maybe you can take better Safari support into consideration anyway? Assuring that all relevant CSS3 properties are also present with the -webkit- prefix might help a lot!

[dmartinezg]

Hey @jcenturion care to join in the discussion?

I understand that the stand alone console (the one out of designer) will be out shortly, I do not want to promise dates, but in the next week or two.

[jcenturion]

We will try to release the new stand alone version in about two weeks.

@meeque, I will reviewing the support for Sarafi and other browsers in depth, thanks.

[maryoush]

We will keep an eye on it on short notice to check whether it solves out problems.

Regards

Sent from iPad

Dnia 17 paź 2014 o godz. 16:34 Javier notifications@github.com napisał(a):

We will try to release the new stand alone version in about two weeks.

@meeque, I will reviewing the support for Sarafi and other browsers in depth, thanks.

— Reply to this email directly or view it on GitHub.

[jcenturion]

@maryoush, @meeque: The new version is now on master. Most of the CSS issues should be fixed, if not just let us know.

Thanks!

[meeque]

Took us some while to get around to this, but now I finally upgraded our service SDK (and some of our services) to the new version. Looks pretty good so far. Thanks for your work!