Thanks Ryan for taking time to investigate this, bug 1674951 as regressor is correct. Updating the sumarry/description to reflect the bug that is windows/mac reproducible (the json string address is not correctly positioned), for which also my windows regression range reliably leads to Bug 1674951: Update the caret position after loading page. r=adw However, there is a 2nd regression or behavior (which messed up the original regression range), which is mac specific and hitting it requires an intermediate step: perform an address bar search, in which case the json address on mac will look like in the bottom part of the original screenshot(blanked out). So far, didn't manage to get something probable as a regression range for that part, but the reason for which I didn't rush to log a spin'off bug is because the regression range for this part is really close to the bug 1674951 one.
Bug 1767053 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Thanks Ryan for taking time to investigate this, bug 1674951 as regressor is correct. Updating the sumarry/description to reflect the bug that is windows/mac reproducible (the json string address is not correctly positioned), for which also my windows regression range reliably leads to Bug 1674951: Update the caret position after loading page. r=adw However, there is a 2nd regression or behavior (which messed up the original regression range), which is mac specific and hitting it requires an intermediate step: perform an address bar search, in which case the json address on mac will look like in the bottom part of the original screenshot(blanked out). So far, didn't manage to get something probable as a regression range for that part, but the reason for which I didn't rush to log a spin'off bug is because the regression range for this part is really close to the bug 1674951 one. I'll get back to this 2nd part on Monday.