Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(59)

Issue 13663043: fix successive conflict UX calls

Can't Edit
Can't Publish+Mail
Start Review
Created:
10 years, 8 months ago by gary.poster
Modified:
10 years, 8 months ago
Reviewers:
rharding, mp+185100
Visibility:
Public.

Description

fix successive conflict UX calls if you set a model value and then set a new one, the newest one will be lost. This branch fixes that problem, and adds a test for simpler conflict UX. https://code.launchpad.net/~gary/juju-gui/fixSuccessiveConflicts/+merge/185100 (do not edit description out of merge proposal)

Patch Set 1 #

Patch Set 2 : fix successive conflict UX calls #

Unified diffs Side-by-side diffs Delta from patch set Stats (+65 lines, -26 lines) Patch
A [revision details] View 1 chunk +2 lines, -0 lines 0 comments Download
M app/views/databinding.js View 2 chunks +5 lines, -0 lines 0 comments Download
M app/views/inspector.js View 4 chunks +34 lines, -26 lines 0 comments Download
M test/test_inspector_constraints.js View 1 chunk +24 lines, -0 lines 0 comments Download

Messages

Total messages: 4
gary.poster
Please take a look.
10 years, 8 months ago (2013-09-11 16:30:27 UTC) #1
rharding
Per irc, tests pass in IE10. Will review as a follow up.
10 years, 8 months ago (2013-09-11 16:43:17 UTC) #2
rharding
LGTM
10 years, 8 months ago (2013-09-11 16:47:57 UTC) #3
gary.poster
10 years, 8 months ago (2013-09-11 17:24:13 UTC) #4
*** Submitted:

fix successive conflict UX calls

if you set a model value and then set a new one, the newest one will be lost. 
This branch fixes that problem, and adds a test for simpler conflict UX.

R=rharding
CC=
https://codereview.appspot.com/13663043
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b