https://bugs.kde.org/show_bug.cgi?id=429635
--- Comment #6 from Oliver Sander ---
I asked Leonard for clarification, and here is his answer:
> To avoid misunderstanding: Do you mean that a reader should process *all*
> actions (in the order you describe), or just the first one?
We should be
https://bugs.kde.org/show_bug.cgi?id=429635
--- Comment #5 from Albert Astals Cid ---
> So I suppose what should be done is process all actions in order. The first
> one will not require special filtering, because executing an empty JS program
> is a no-op.
I don't think that is what Leonard
https://bugs.kde.org/show_bug.cgi?id=429635
--- Comment #4 from Oliver Sander ---
Here is his answer:
"The order of the Annotations in the Annots array in the page dictionary
defines the order in which rendering and hit testing is performed. However,
there is nothing that precludes you doing w
https://bugs.kde.org/show_bug.cgi?id=429635
--- Comment #3 from Albert Astals Cid ---
Sure, ask away
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=429635
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=429635
Albert Astals Cid changed:
What|Removed |Added
CC||aa...@kde.org
--- Comment #1 from Albert As
