#7416 closed defect (bug) (fixed)
Fix for profile image upload on Microsoft Edge breaks iOS Safari and Chrome
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 2.9 | Priority: | normal |
Severity: | normal | Version: | 2.7.3 |
Component: | Core | Keywords: | has-patch |
Cc: |
Description
This is a follow-up to #7360.
I'm running BuddyPress 2.7.4. A user of my site reported that avatar uploads weren't working on iOS, and I noticed that sure enough, the moxie-shim was no longer in alignment.
I tracked it down to the recent change to avatar.min.css, which overrides the positioning as a fix for alignment on Microsoft Edge. However, it seems to break alignment on my site on iOS Safari and Chrome (as tested via Chrome's device toolbar).
.moxie-shim.moxie-shim-html5 { top: 108px !important; left: 40.1% !important; width: 12em; }
This is easy enough for me to revert locally to restore proper alignment (though probably breaking MS Edge again, which I don't have to test against), but thought I'd report it here in case I'm not the only one experiencing it.
Attachments (1)
Change History (16)
#3
@
8 years ago
I've seen a few support threads about this in the forums about the Microsoft Edge fix affecting mobile browsers.
Perhaps we should use an Edge CSS hack to target Edge only.
#4
@
8 years ago
- Keywords has-patch added
@benjlipchak - Can you try the patch above and see if it fixes things for iOS Safari? I don't have an iOS device so I cannot check.
#5
@
8 years ago
Problem with hacks is they tend to point to the fragility of the original concept but if the @media query works fair dues, I perhaps should have considered something like that in the original quick fix. Given our stretched time & resources I would probably consider effects like this better toned down where smaller devices are concerned.
This ticket was mentioned in Slack in #buddypress by hnla. View the logs.
8 years ago
This ticket was mentioned in Slack in #buddypress by r-a-y. View the logs.
8 years ago
#10
@
8 years ago
@mrjarbenne was able to confirm that the fix works.
The patch above only works for sites with SCRIPT_DEBUG
set to true
:) When we release the new version, grunt will generate the proper minified version of the CSS file.
Going to commit this.
#12
@
8 years ago
- Owner set to r-a-y
- Resolution set to fixed
- Status changed from new to closed
In 11579:
#13
@
8 years ago
So I figured out a way to remove all the CSS hacks we were using and to fix this at the JS level.
Thanks to everyone for helping debug this issue.
Those changes were admittedly a short term solution or quick fix but I did test them as far as possible in various browsers and in Chrome I don't see the issue you're describing.
We probably would need more detail before being able to tackle any solution I would need to be able to replicate the issue locally.
It may be best short term to override the styles yourself to provide a fix that works for your users. longterm as I mentioned on the other ticket probably means unpicking the build, html/css, and re-factoring it to be a little more robust.