Opened on 07/29/2016 at 12:21:31 PM
Closed on 07/09/2019 at 07:09:27 PM
#4276 closed defect (rejected)
Adblock Plus for Safari causing elements to be positioned incorrectly
Reported by: | abstractourist | Assignee: | |
---|---|---|---|
Priority: | P4 | Milestone: | |
Module: | Platform | Keywords: | |
Cc: | kzar, sebastian | Blocked By: | |
Blocking: | Platform: | Safari | |
Ready: | yes | Confidential: | no |
Tester: | Unknown | Verified working: | no |
Review URL(s): |
Description (last modified by kzar)
Environment
- ABP 1.12.1 in Safari 9.1.2 (10601.7.7) on OSX 10.10.5
- No other extensions installed.
- No filters or subscriptions at all.
How to reproduce
- Browse to https://www.timum.de/singleResource/019d0650-54c4-11e6-85a9-02c1f4331137
- Click the question mark in the footer
Observed behaviour
The bootstrap popover appears shifted down by 50%:
Expected behaviour
Attachments (0)
Change History (7)
comment:1 Changed on 07/29/2016 at 01:11:01 PM by mapx
- Cc kzar sebastian added
comment:2 Changed on 07/29/2016 at 02:33:10 PM by abstractourist
comment:3 Changed on 10/12/2016 at 02:26:35 PM by kzar
- Component changed from Unknown to Platform
- Priority changed from Unknown to P3
- Ready set
Can reproduce as described.
comment:4 Changed on 10/12/2016 at 02:31:19 PM by kzar
- Description modified (diff)
- Summary changed from No content blocked, but bootstrap popover shifted to Adblock Plus for Safari causing elements to be positioned incorrectly
comment:5 Changed on 01/19/2017 at 02:08:55 PM by abpbot
(Wrong issue was referenced, commit was for #4726)
Last edited on 01/19/2017 at 02:13:00 PM
by fhd
comment:6 Changed on 09/13/2017 at 04:38:37 PM by sebastian
- Priority changed from P3 to P4
comment:7 Changed on 07/09/2019 at 07:09:27 PM by sebastian
- Resolution set to rejected
- Status changed from new to closed
I'm closing all issues related to the legacy Safari extension, as it has been discontinued in favor of an App Extension that doesn't share any code with the old extension.
Note: See
TracTickets for help on using
tickets.
Ah and by the way the problem does not occur in Chrome 51.0.2704.103