Closed Bug 736627 Opened 13 years ago Closed 13 years ago

Showing a list of environments in case conductor in environments section causes major portions of the site to be lost in rendering

Categories

(Firefox Graveyard :: Webapp Runtime, defect)

defect
Not set
major

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: jsmith, Unassigned)

References

()

Details

Attachments

(1 file)

Steps: 1. Go to https://caseconductor-dev.allizom.org 2. Login with an account (register an account if you need to get one) 3. Go to Environments 4. Select one of the right arrows to drop down the list for more details about an environment Expected: See the right portion of the screenshot. You should see the site maintain its main layout, along with showing the details of a particular environment. Actual: See the left portion of the screenshot. The rendering for the site is completely lost, with only showing the environments on a white background with no CSS. Many of the HTML that was the original page was lost too. At this point, without a back button, I have to restart the app in order to recover.
Whiteboard: [runtime]
Component: General → Desktop Runtime
Whiteboard: [runtime]
Blocks: 737571
Whiteboard: [marketplace-beta?]
Whiteboard: [marketplace-beta?]
Whiteboard: [marketplace-beta-]
Keywords: qawanted
Isn't this a case conductor bug? I don't see how this is at all related to webapps? Waiting to hear from Jason before I move components.
(In reply to Clint Talbert ( :ctalbert ) from comment #2) > Isn't this a case conductor bug? I don't see how this is at all related to > webapps? Waiting to hear from Jason before I move components. I can explain how this is a web apps bug. See the screenshot. There are bugs in the case where the web application will render or work correctly in desktop firefox and correspondingly work incorrectly in the desktop runtime. This usually means it could be one of two issues: - A problem within the application that we need to evangelize - A problem within our platform The loss of rendering only the desktop runtime likely our problem, as it does not correspondingly happen on firefox. I need to retest this though, cause this may be fixed in the new implementation.
ok cool. Thanks for the explanation. Now I follow you.
Cameron - Let me know when OWA support gets enabled on dev. I'd like to retest this bug to see if it happens on the new implementation on nightly.
No longer blocks: 737571
Whiteboard: [marketplace-beta-]
Component: Desktop Runtime → Webapp Runtime
Product: Web Apps → Firefox
Confirmed that this bug is no longer valid.
Status: NEW → RESOLVED
Closed: 13 years ago
Keywords: qawanted
Resolution: --- → INVALID
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: