Bug 984460 comment 52.

Comment on attachment 8411180 [details] [diff] [review] patch Review of attachment 8411180 [details] [diff] [review]: ----------------------------------------------------------------- Fine by me although I probably would have modified SetDisplayPortBase to take a priority value instead, to keep it parallel to SetDisplayPortMargins and SetDisplayPortForElement.

That didn't occur to me. But it seems a little silly to keep a value around that we know is wrong. Also, how do we manage priority levels? AZPC for display port base uses 0, layout uses 1, testing using 2? It would get more confusing then it needs to be I think.

Yeah that's probably what I would have done (wrt managing priority levels). But it doesn't matter, you can land the patch you have. If we decide later we want something different it's not hard to change.