Member Avatar for sganandhsg

Hi All,

We are using zetta cube with asp.net and vb.net (coding) in 3.5 framework / VS 2008 from 2010. Its working fine. Just 3 months back we are upgraded to IE11 (Edge mode) at the time of upgrading we faced some of UI issues and resolved the same.

The same way we facing issues in Zetta cube also, earlier IE version working good.

The issues is totally, we have separated 3 panels, once launched the URL it will launch all three panel based on the functionalities. When click to Pin / Unpin the panels, that panel get cleared (shown white page) we have analysed and didn’t get correct fix on this. Please help?

I have attached sample project in this with Left, Centre and Right panels. Please take a look and you will get clear idea of the problem

Thanks,
Anandh

ZettaCubeWithASP.zip (212.64 KB)
  • 2 Contributors
  • 1 Reply
  • 455 Views
  • 5 Days Discussion Span
  • Latest Post Latest Post by rproffitt

Dani AI

Generated

reported that after upgrading to IE11 (Edge mode) a Zetta Cube layout with left/center/right panels shows a blank (white) panel when a panel is pinned or unpinned. As noted, first-stage triage should confirm whether this is IE-specific (test in Chrome/Firefox and run a markup/CSS validator) so effort focuses on a renderer issue versus malformed HTML or a server-side problem.

A focused IE11 debugging checklist (use F12):

  • Watch the Console and Network panels for exceptions or failed resources during the pin/unpin action.
  • Inspect the DOM after the panel goes blank to confirm the nodes still exist; check computed styles (display, visibility, opacity, height, z-index).
  • In Emulation, try different Document Modes to see whether behavior depends on document mode.
  • Put breakpoints in the pin/unpin handler and log element.innerHTML, childNodes.length, and computed styles to see whether content is removed or only hidden.
  • Reproduce in a minimal static page (strip server-side code) so the library + markup are isolated.

Common root causes and quick workarounds: older UI kits often rely on IE-specific behavior or wrong feature detection and can end up detaching/re-attaching nodes or changing styles in a way modern IE handles differently. Forcing a repaint after the unpin can cure rendering glitches:

var p = document.getElementById('leftPanel');
p.style.display = 'none';
p.offsetHeight;               // force reflow
p.style.display = 'block';
p.style.zoom = '1';           // IE repaint hint
p.style.transform = 'translateZ(0)'; // force composite

Also verify a proper standards DOCTYPE and any X-UA-Compatible header/meta that might change document mode. If the minimal repro still fails in IE11, it likely points to a library compatibility bug (incorrect event-model branching or DOM manipulation). A concise reproducible test case containing the panel markup, the pin/unpin handler, and the F12 console snapshot will make further diagnosis or a vendor patch practical.

Member Avatar for rproffitt

This one looks to be one of those issues where so few are using your kit (collection of tools) that the answer may be to go with what works.

But first I see you posted weeks ago at and maybe other places. That's fine since you gave time to those other places. No problem there but it does lead me to beleive you are in a rare spot.

Since this looks very very specific to some company or such application, find any exit. That is, test in Chrome, Firefox and be sure your web page gets a clean pass of w3c's tester.

It's a long shot to find someone with all those dev tools and a server so you may have to use any exit.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.