While discussing our duplicate detection behavior for in-band cues on the HTML mailing list, this came up: > Ok. So existing WebKit behavior will add the cue again if the application > modified it. That is likely to be surprising to the application developer. > We definitely need clarification on what the proper behavior should be in > the spec. I think the way we should handle this is by comparing cues with the original cue content, not the current cue content, so if we seek backwards and see a cue that already exists, but has been modified, we ignore that cue and just keep the modified one.