[#18723] - [4.0] Cannot read property 'addEventListener' of null - passwordview.min.js
- Closed
- 20 Nov 2017
- Medium
- Build: staging
- # 18723
Steps to reproduce the issue
Install 4.0 alpha 2
in Admin Users Options -> set Display Labels = Text (thats the green and not grey option of the incredibly difficult to understand toggle boxes!)
Go to the frontend and reload the home page (which has a login module by default on the right)
Expected result
No JS errors in console.
Actual result
Error message in console
Uncaught TypeError: Cannot read property 'addEventListener' of null
at HTMLDocument.<anonymous> (passwordview.min.js?027cdb66b159c72b9497be415bbbd127:1)
System information (as much as possible)
Additional comments
joomla-cms-bot
- | Labels |
Added:
?
|
||
| Category | ⇒ | com_users JavaScript |
| Status | New | ⇒ | Confirmed |
Javascript team is working on another approach for ALL fields that are js dependant so that they'll be implemented as custom elements (check the user field and the media field). So this is WIP and again can be marked as known issue
We need Information what to test, what not now. I suggest on Download-Page like https://github.com/joomla/joomla-cms/releases/tag/4.0.0-alpha2
Yes, simply saying this is a "known issue" because you have some secret plans that you are not sharing with anyone is simply a waste of testers time....
There is nothing about these secret plans on
@PhilETaylor there is nothing secret, so please stop repeating this. I've mentioned the 2 fields that are already implemented in j4 and since you're asking here is the public code that we're working on:
https://codepen.io/dgt41/
I was asked to test the Alpha, I did. This (and multiple other JS issues) is a problem with that has been confirmed with the alpha.
There was nothing about this being a "known issue" - its only "known" to you, it is not on a list of known issues... This "known issues" list should be a public document, or at least on one of the urls above which is the correct place for known issues to be listed.
You cannot just close issues stating YOU alone know about things...
These issues should remain open until the "javascript team" implement their secrets, and confirm that the feature/bug/report reported is either a) No longer relevant, or b) fixed.
Closing issues and simply ignoring them is what happens else.
actually the request was to test alpha with extensions
There is one goal for this release: to allow advance testing of custom extensions so that extension developers can report any problems well before the final release.
@PhilETaylor where did I state that this issue should be closed?
I just said that this should be marked as known issue and tried to justified the reason for that...
Its funny how every conversation with @dgt41 turns into this pathetic tirade. I tell you what - I'll NEVER test JS or Custom Elements ever again. Job solved.
actually the request was to test alpha with extensions
tldr; I guess, as I have not even installed an extension to an alpha...
here is the public code that we're working on
Is there a Public, Joomla user hosted, GitHub Repository for this?
| Status | Confirmed | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-11-20 14:54:30 |
| Closed_By | ⇒ | PhilETaylor |
Issue confirmed. Set on Module "Login Form" the "Display Labels".
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/18723.