[#22186] - [4.0] Make Notification Dropdown viewable.
- Fixed in Code Base
- 17 Sep 2018
- Medium
- Build: 4.0-dev
- # 22186
- Diff
- N6REJ:4.0-dev
User tests: Successful: Unsuccessful:
Pull Request for Issue #22118 .
Summary of Changes
Will cause notifications to be above the headers.
Testing Instructions
go to extension manager click on notification bell in top right.
drop down will be obscured by header.
install patch
now drop down will be above the header
Expected result
Actual result
Documentation Changes Required
none
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Administration Templates (admin) |
| Title |
|
||||||
install patch
Please tell the people that pr is not testable with patchtester. Needs npm.
Please tell the people that pr is not testable with patchtester
needs a Select for PR-Creator if Patchtester can be used.
Please tell the people that pr is not testable with patchtester
needs a Select for PR-Creator if Patchtester can be used.
I'm going to be real honest here. The issue tracker is very underutilized in relation to just using GitHub (the traffic stats for this repo are exponentially higher than the traffic stats for the entirety of the issue tracker subdomain, like the traffic for one day on GitHub exceeds one week on the tracker). Given the project's limited resources, especially when it comes to things outside the CMS' development (look how few contributors we have to the .org apps or the Joomla Framework repos or com_patchtester itself), we're better off investing time into a carsonbot type solution or any of the existing bots in the GitHub ecosystem than doing another round of heavy investment of time and resources into the tracker.
+1 for whatever Solution provide 1 instead 2 Sources to maintain.
install patch
Please tell the people that pr is not testable with patchtester. Needs npm.
Sorry about that, It's for 4.0-dev which requires npm to build from git so I assumed that was enough.
I have tested this item
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/22186.
| Title |
|
||||||
| Status | Pending | ⇒ | Ready to Commit |
RTC
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/22186.
I think this should be fine!
| Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-09-17 11:30:05 |
| Closed_By | ⇒ | wilsonge | |
| Labels |
Added:
?
?
|
||
Perfect. Thanks guys!
Yes, because when start throwing around with z-indexes without a plan we will get sooner or later into a mess
Using $zindex-* variables could help a bit to get rid of too many different values.
I have tested this item✅ successfully on fb1771a
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/22186.