IE 8 Click on form action control from frontend. E.g. Profile edit from click save or cancel
Form should finish action
IE 8 error - some forms are ok others will stop working. error message :
object doesnt support this action html5fallback.js char 1939
Joomla 3.5.1
Have investigated a bit
in the html5fallback.js
there seem to be some commas where semicolons are expected g.isRequired=!!g.required,g.isDisabled=!!g.disabled,g.isDisabled||
switched to the uncompressed file and alerted to line:122 char5
elem.isDisabled = !!elem.disabled;
commenting this line out generates no errors and the forms work normally.
Category | ⇒ | JavaScript |
Title |
|
I don't thinks so,
swapped the .js file for https://github.com/okonomiyaki3000/joomla-cms/blob/108cfdbfb10d0370fb0a4bdeed8c3e3e5c564fdb/media/system/js/html5fallback-uncompressed.js
error this time line 161 same bit of code
elem.isRequired = !!elem.required;
elem.isDisabled = !!elem.disabled;
Labels |
Added:
?
|
No console log error is produced Joomla 3.6, so it has already been fixed
I will give it a check in IE 8 later
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-07-14 13:22:42 |
Closed_By | ⇒ | kirancheema |
Status | Closed | ⇒ | New |
Closed_Date | 2016-07-14 13:22:42 | ⇒ | |
Closed_By | kirancheema | ⇒ |
Just to say that the error above happened using the standard option=com_users
Site was updated to J3.6 yesterday
so this is not a barebone J3.6 installation,
I don't say that this is not a IE8 bug / issue,
Hi George,
Close was clicked by accident, have opened again.
This issue is happening on every Joomla 3x series install that I have .
did a Vanilla 3.5.1 just last week and the same error occurs in IE8. on vanilla (any) frontend forms with no extensions installed and default protostar template.
Will do a vanilla 3.6 from scratch later today if i get a chance and report back
Will do a vanilla 3.6 from scratch later today if i get a chance and report back
@kirancheema please can you update this. If not this issue will be closed in a few weeks
Status | New | ⇒ | Information Required |
Vanilla 3.6.2 install done today.
Can confirm the above error is still occurring with IE8 .
-> index.php?option=com_users
Exactly the same error as above.
Same issue with editing the users profile page.
let me know if you want screen shots..
I still cannot replicate this issue on IE8. Have tested both in the frontend and backend. I assume you have cleared your browser cache.
I have indeed cleared browser cache etc.
Am using real IE 8 and not IE 8 Mode.
With the Standard login forms you will see them Alert the errors if you turn debug mode on but the pages will redirect ..
Main issue has been caused when creating custom forms to submit over ajax ....
@kirancheema turn on Debug mode for Joomla, and check on which line exactly the error
Somehow this still seems to be relevant and actually does not only occur ith IE8 but also with IE11. I have been able to reproduce this issue on several machines and several different Jomlla installations.
Apparently the uncompressed version works fine but when the code is compressed, a comma is iintroduced where the IE11 ECMAScript compiler expects a semicolon (I guess). When in the compressed code, character 1550 is replaced by a semicolon the code does not cause any more errors. Or when removing the "use strict" line, but I doubt that this is something we want to do.
Is there something that can be done when compressing the files that will prevent this from becoming a problem?
@alexvanniel - I'm still unable to replicate this on IE8 or IE11. I've tried going to my profile and click save/close, along with other forms in the frontend. How did you replicate it?
Mmm, I am getting a different error message but on the same lines and I think the issue revolves around the same problem. I am getting "Assignment to read-only properties is not allowed in strict mode" for the elem.isDisabled = !!elem.disabled; statement.
I managed to track the problem down to an input field that was set to "disabled". So you need to find a form that has an input field set to "disabled" and submit that form. You will get the above mentioned error message, or the one mentiomned in the original issue.
If I go to edit my profile, the Username
field is already disabled, but still not getting the error
That is because the field actually is set to readonly="readonly" and not set to disabled="disabled". It only seems to happen when the input has an attribute "disabled" set. I am trying to find an input where this is actually still used but it seems that "disabled" has been removed from or is not in use anymore in almost all input fields.
I also tried setting the email field to disabled
, still nothing :/
When you inspect the element in either Chrome or Internet Explorer, does it actually carry the disabled attribute?
yes, it's there.
Try for yourself
components\com_users\models\forms\profile.xml
<field
name="name"
type="text"
label="COM_USERS_PROFILE_NAME_LABEL"
description="COM_USERS_PROFILE_NAME_DESC"
filter="string"
required="true"
size="30"
disabled="true" <<< Here
/>
I am stumped. For me it happens in IE11 when an input is set to disabled (not just readonly) and the form is validated. It seems we are at an impasse.
Maybe this can help. It does not seem to happen when editing a single item but on lists. For instance if you have an input field anywhere within the form of the list view that is set to disabled and you try to change the sort order. I have narrowed the issue for me down to an input field in a modal window for batch processing. It seems not to happen with vanilla Joomla components but with a modified batch processing modal form for some custom component.
Status | Information Required | ⇒ | Discussion |
After 1 year I am closing this issue. No one has been able to replicate it with core joomla. If someone can reproduce this on a clean install with the latest release then it can always be reopened
Status | Discussion | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-08-18 10:22:08 |
Closed_By | ⇒ | brianteeman | |
Labels |
Added:
J3 Issue
|
Can you check and see if #6409 fixes it