Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

My Alerts wysiwyg editor not shaded on alerts pop-up #2441

Closed
euantorano opened this issue Jun 29, 2016 · 7 comments
Closed

My Alerts wysiwyg editor not shaded on alerts pop-up #2441

euantorano opened this issue Jun 29, 2016 · 7 comments
Labels
s:rejected Status: Rejected. Invalid report / request which will not be addressed

Comments

@euantorano
Copy link
Member

euantorano commented Jun 29, 2016

When you're on a page with the wysiwyg editor and click on "View Alerts", the alerts pop up and it gets highlighted, while the background becomes shaded (totally fine so far). but then the wysiwyg editor is not shaded, its still lighted.

Screenshot: http://image.prntscr.com/image/e715f667f90b41aeb22f752c2b2b9c44.png

Original thread: My Alerts wysiwyg editor not shaded on alerts pop-up

@euantorano euantorano added t:bug Type: Bug. An issue causing error / flaw / malfunction s:confirmed Status: Confirmed. Retested and found the issue exists b:1.8 Branch: 1.8.x labels Jun 29, 2016
@Destroy666x
Copy link
Contributor

Destroy666x commented Jun 30, 2016

Is this surely in the correct place? Modals have a high z-index by default, which seems to shade it.

@Destroy666x Destroy666x added s:feedback Status: Feedback. Further information/input needed and removed s:confirmed Status: Confirmed. Retested and found the issue exists labels Jun 30, 2016
@euantorano
Copy link
Member Author

@Destroy666x I was talking about this on Slack last night. MyAlerts by default uses MyBB's built in modals. I tested on a near stock forum and the MyAlerts modal was given a z-index of 2, the mask was given 1, and the editor was given 3.

My test board is using the old approach of using rel="modal" rather than an onclick handler though, so I need to update the templates there to use onclick the same as the buddylist does in the standard theme. Once I've checked that, I can either confirm or close this issue.

@Destroy666x
Copy link
Contributor

Destroy666x commented Jun 30, 2016

It'll definitely work with the same onclick because our wrapper function takes care of it: https://github.com/mybb/mybb/blob/feature/jscripts/general.js#L75. As for fixing the rel method, we could do it by extending $.modal, but MyBB.popupWindow() should be used as a standard by devs IMO.

@euantorano
Copy link
Member Author

Alright, it's probably easiest to leave it as is then. I'd rather not go extending/patching third party stuff for 1.8.8.

@Destroy666x Destroy666x added s:rejected Status: Rejected. Invalid report / request which will not be addressed and removed b:1.8 Branch: 1.8.x t:bug Type: Bug. An issue causing error / flaw / malfunction s:feedback Status: Feedback. Further information/input needed labels Jun 30, 2016
@ghost
Copy link

ghost commented Jul 2, 2016

Why was this rejected so? @euantorano already provided a fix for it, editing the myalerts_headericon template and having the latests alert.php file installed on the server.

@Destroy666x
Copy link
Contributor

Umm... You kind of answered yourself. This is not MyAlerts repository.

@ghost
Copy link

ghost commented Jul 2, 2016

Oh ok, why was it posted here anyway then. :P

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
s:rejected Status: Rejected. Invalid report / request which will not be addressed
Projects
None yet
Development

No branches or pull requests

2 participants