chitochi
Shadow not rendering on web in a mobile layout
I have inset shadows that render fine in web, as long as the layout is "desktop" like. When I either open it on my phone or when I use the debugger in web to force it into a mobile layout the shadows disappear entirely. I have no clue what could be causing this, any thoughts?
Damn sorry I adhded my way out of this issue. :laughing:
Thank you for opening this issue, sorry for the delay of my answer!
I haven't done much testing of the web platform to be honest. I have no idea of the cause of this bug, I will try to take some time to reproduce it, but I am not sure when.
If you find anything that could help, don't hesitate! :pray:
(If you could try again using the latest version of the flutter_inset_shadow package (not flutter_box_inset_shadow), that would be really great.)
I'm also facing this issue. Love the package and the way it gives shadows on desktop but it doesn't have the same effect on mobile. I have a word game where I am using this. Here are two images which highlight the difference. I am using flutter_inset_shadow 2.0.3
On Desktop:
On Mobile:
Any help is appreciated
Hi, sorry I don't know why but I wasn't subscribed to that issue so I didn't received the notification.
Thank you for the screenshots, I will take a look at this again.
Just to be sure, when you say mobile you mean web on a mobile?
Yes I mean web (browser) on mobile
Regards, Radha
On Fri, Sep 27, 2024, 16:02 Chito @.***> wrote:
Hi, sorry I don't know why but I wasn't subscribed to that issue so I didn't received the notification.
Thank you for the screenshots, I will take a look at this again.
Just to be sure, when you say mobile you mean web on a mobile?
— Reply to this email directly, view it on GitHub https://github.com/chitochi/flutter_inset_shadow/issues/12#issuecomment-2378967721, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJAJ3U24JJO5L5THEUYMPBTZYUX4XAVCNFSM6AAAAABJ5HBRGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZYHE3DONZSGE . You are receiving this because you commented.Message ID: @.***>
Thanks for filing this. I was scratching my head as to why it wasn't working in Chrome and it hadn't occurred to me that the problem might have been the platform.
