PDA

View Full Version : [NOREPRO] ExtJS 6.0.0.415 beta Cannot read property 'ariaEl' of null



raphael.franchet
19 Jun 2015, 8:02 AM
When I have a border layout, with a collapsible panel at north. I have a js error when expanding it.

In the under exemple, collapse the top panel and expand it. Have a look at your console,

Uncaught TypeError: Cannot read property 'ariaEl' of null

(note that if hideCollapseTool is false, everything works fine)

As fiddle is not working with extjs6, please add the following file in the "examples" directory


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">


<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta content="IE=edge" http-equiv="X-UA-Compatible" />
<title>Extjs</title>
<link rel="stylesheet" type="text/css" href="../build/classic/theme-gray/resources/theme-gray-all-debug.css"/>


<script src="../build/ext-all-debug.js" type="text/javascript"></script>
<script src="../build/classic/locale/locale-fr-debug.js" type="text/javascript"></script>
<script src="../build/classic/theme-gray/theme-gray-debug.js" type="text/javascript"></script>

</head>


<body>
<script>
Ext.application({
name : 'Fiddle',

launch : function() {
Ext.create("Ext.container.Container", {
renderTo: Ext.getBody(),
layout: 'border',
height: 400,
border: true,
items: [
{
xtype: 'component',
html: 'toto'
},

Ext.create("Ext.panel.Panel", {
title: 'Click me to collapse me and reclick to expand me',

region: 'north',

collapsible: true,
hideCollapseTool: true,
titleCollapse: true,
animCollapse: false,



items: [
{
xtype: 'component',
html: 'Contenu'
}
]
})
]
})
}
});
</script>
</body>
</html>




I also had a similar issue, but I cannot manage to reproce it here with the folowing trace:

Uncaught TypeError: Cannot read property '_ariaRole' of null
Ext.define.doPlaceholderExpand @ ext-all-debug.js:136285

evant
19 Jun 2015, 7:39 PM
I can't reproduce this with the latest nightly, it appears this has already been resolved.