You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Ben Keen (JIRA)" <ji...@apache.org> on 2014/11/18 00:11:33 UTC

[jira] [Work started] (COUCHDB-2458) Changing routes shouldn't force repaint of everything in route

     [ https://issues.apache.org/jira/browse/COUCHDB-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on COUCHDB-2458 started by Ben Keen.
-----------------------------------------
> 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)