Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug 994146: Panel should be reset when closed. #19

Merged
merged 1 commit into from May 5, 2014

Conversation

n1k0
Copy link

@n1k0 n1k0 commented Apr 28, 2014

@dmose
Copy link
Collaborator

dmose commented Apr 29, 2014

Apologies, I didn't get a chance to poke at this today. I felt like I had to give priority to the various architecture untangling, since that's really the long pole in the tent. :-(

document: fakeDocument
});
}

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clever; I like this testing methodology!

@dmose
Copy link
Collaborator

dmose commented May 5, 2014

Out of curiosity, why does it make sense for the panel to have a router at all? Is there really likely to be more than one full-page view for the panel? Or is this to it easier on the shared code stuff? I suspect there's nothing worth changing here; this question is more for my own understanding.

@dmose
Copy link
Collaborator

dmose commented May 5, 2014

Looks good, r=dmose with any appropriate stuff addressed.

@n1k0
Copy link
Author

n1k0 commented May 5, 2014

Out of curiosity, why does it make sense for the panel to have a router at all?

For two reasons; the first one is to ensure consistency across the different project apps (webapp, panel & conversation window). The second is to ensure easing further evolutions for the panel, eg. adding support for the contact list and so on.

@n1k0 n1k0 merged commit e12cdb6 into loop-ui-initial May 5, 2014
@n1k0 n1k0 deleted the bug-994146-panel-reset-when-closed branch May 5, 2014 08:27
ekr added a commit that referenced this pull request Sep 18, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants