Closed vivekhub closed 5 years ago
I don't know if it's something you can record, but if you can supply a video of the problem, that would be incredibly helpful. I don't think much of this has been optimized for mobile in general yet, but I'm planning some effort in that direction. I'll see about replicating rotation issues on my iDevices.
I think we dont have problem with mobile devices right now, but when a resizing (rotating is a resizing actually) happens. However, as @casiotone said before, we're trying to make the IntroJs compatible with mobile devices also.
I was trying the sample page and was unable to read the third note, since my browser was nit allowing me to scroll to the left. However, I was able to scroll to the right - but that's still quite ugly. Maybe the balloons should always be presented above/below the element in mobile settings? The screenshot attached is of Chrome in a Nexus 7.
Here are some more screen shots from my nexus 7 tab On Mar 28, 2013 6:48 AM, "Igor Santos" notifications@github.com wrote:
I was trying the sample page and was unable to read the third note, since my browser was nit allowing me to scroll to the left. However, I was able to scroll to the right - but that's still quite ugly. Maybe the balloons should always be presented above/below the element in mobile settings? The screenshot attached is of Chrome in a Nexus 7. [image: Screenshot_2013-03-27-22-12-30]https://f.cloud.github.com/assets/532299/311503/420f7000-9745-11e2-85de-635886461752.png
— Reply to this email directly or view it on GitHubhttps://github.com/usablica/intro.js/issues/62#issuecomment-15563243 .
I'm also having some problem on mobile right now (Android 2.3.4).
On the Android Browser (v2.3.4), the overlay doesn't take the whole body but only the section of the page visible to the user. So when scrolling, there are parts of the page that are not cover by the overlay.
On Opera Mini (v 7.0.3), the overlay isn't displayed at all. Also for some reason, click on next/previous reloads the whole page.
Thanks @igorsantos07 and @vivekhub for screenshots, pictures are more obvious. Thanks for detailed report @cotenoni, I will mark this conversation as bug and I will work on it for next versions.
@afshinm thanks - let me know if you want me to test on a few android devices.
I've been building a test app of intro.js to use on androids so be glad to share the results when its completed
On Tue, Apr 9, 2013 at 6:33 AM, Vivek Venugopalan notifications@github.comwrote:
@afshinm https://github.com/afshinm thanks - let me know if you want me to test on a few android devices.
— Reply to this email directly or view it on GitHubhttps://github.com/usablica/intro.js/issues/62#issuecomment-16107427 .
Hmm those LinkedIn comments are very disturbing. Surprised they haven't been deleted yet.
Anyway, I am just wondering if there is any progress on Mobile Compatibility. Thanks.
We're also experiencing the same problem where the tooltip goes off the viewport. This isn't necessarily a mobile problem, the same goes for a full width layout. Putting the tooltip on top/bottom doesn't always fix it either, the tooltip can still go off viewport if it's wider than the target element.
Thanks.
Any progress on this one?
@teo-sk In our latest versions we have more mobile/tablet support. Do you have any issues with v0.5?
This issue still exists. I have no config options set except data-intro
and data-text
for the DOM element. I also turned off the red numbers.
I'm having the same problem. Modals cut off in mobile viewport screens.
I see the same as well.
Any solution on this? Or maybe a way of allowing another position when on a different resolution?
Sorry about the linkedin posts. Look like an app I was testing selected the wrong account. Comments have been deleted.
Is this bug only in v0.5 or have has been fixed?
Is there an update on this issue?
Mockup proposal to intro.js interaction in mobile.
The mockup of @valessiobrito is very nice. Though might be problematic in case of a fixed footer/header one wishes to highlight.
Anyway, I would also fancy improved mobile support big time!
+1 :-)
+1 :+1:
:+1:
I have similar problem but it happens to a page with long scrolling in mobile.
+1 for @valessiobrito mock-up
and i'd like to add idea to solve @rhulshof concern. in case of the target element's position is fixed on top of the page, then the message is also a fixed layout and the whole page move down so it's not on top of the element.
I will work on this to add for the next versions.
Will this be supported on mobile devices? Seeing strange issues on android on screen resolution changes during device rotation