[
https://issues.apache.org/jira/browse/COUCHDB-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Keen resolved COUCHDB-2458.
-------------------------------
Resolution: Won't Fix
On further investigation, I'm going to put this down as a "won't fix" for now.
The most noticeable instance of this problem is with the breadcrumbs on the
documents page, and that's occurring there because the custom breadcrumb header
isn't smart enough to know when to redraw itself - but it's some super simple
logic to add. I'll create a separate ticket for that.
> Changing routes shouldn't force repaint of everything in route
> --------------------------------------------------------------
>
> Key: COUCHDB-2458
> URL: https://issues.apache.org/jira/browse/COUCHDB-2458
> Project: CouchDB
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Fauxton
> Reporter: Ben Keen
> Assignee: Ben Keen
>
> This is an old issue. Basically the way Fauxton works is that going from page
> to page within a particular route causes a re-render of everything - even
> headers. This is both unnecessary from an end user standpoint (the header
> doesn't need to change in many cases) and a bit unsightly (the header flashes
> as it's redrawn).
> I'd like to improve this so that route changes only cause repaints of
> whatever you want (e.g. the main body) and not everything. It should allow
> you to fine-tune exactly what needs redrawing on route changes, and what can
> be preserved. There should be a way to re-render the preserved Views as
> needed.
> I have something in mind which I'll put in a PR and open up for discussion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
