Pooja Parihar created TRINIDAD-2526:
---------------------------------------

             Summary: Parent page not getting disable on opening child window 
using modal dialog.
                 Key: TRINIDAD-2526
                 URL: https://issues.apache.org/jira/browse/TRINIDAD-2526
             Project: MyFaces Trinidad
          Issue Type: Bug
          Components: Components, Facelets
    Affects Versions: 2.1.0-core
         Environment: Windows 7 64-Bit
            Reporter: Pooja Parihar


The Core JavaScript file considers IE11 and Chrome39 as a Gecko and Safari 
browsers respectively.
The JavaScript agent initialization (function _agentInit ) uses the userAgent 
property of the DOM's navigator object to identify the browser and its version 
number. This function use ‘msie’ to identify IE agent. Below are the userAgent 
for the browsers involved :
IE 11            - "mozilla/5.0 (windows nt 6.1; wow64; trident/7.0; slcc2; 
.net clr 2.0.50727; .net clr 3.5.30729; .net clr 3.0.30729; media center pc 
6.0; .net4.0c; .net4.0e; rv:11.0) like gecko"
Chrome 39 - "mozilla/5.0 (windows nt 6.1; wow64) applewebkit/537.36 (khtml, 
like gecko) chrome/41.0.2272.76 safari/537.36"
IE8               -  "mozilla/4.0 (compatible; msie 8.0; windows nt 6.1; wow64; 
trident/4.0; slcc2; .net clr 2.0.50727; .net clr 3.5.30729; .net clr 3.0.30729; 
media center pc 6.0; .net4.0c; .net4.0e)"

As IE11 and Chrome39 userAgent doesn’t Contain “msie”, the 'isIE' attribute is 
set to 'false' for these browser.

On accessing child window using modal dialog, openWindow() function of 
Window.js under trinidad-impl-2.1.0\META-INF\adf\jsLibs is called.
This  method executes different blocks depending on the whether the browser is 
of type – IE, Gecko, etc.
-       For with IE8 , the block for IE browser executes (which contains code 
responsible for dimming of parent page).
-       For IE11 and Chrome 39, IE block doesnot executes (ie, code for dimming 
parent page is not executed).




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to