Hi Roman,
I thought there was a reason behind this :) Still, having a PreviousFrame() method would be great, if it can take care of all the things needed to make it work. With codecs that do not support it, the performance would possibly not be great, or it would not work at all, but that way developers would not have to manually handle the codec specifics. If the drawbacks are well documented, this should not be an issue.
Having a way to find out if the currently playing media supports seeking backwards could make it possible to adjust the UI and inform the user as needed. A boolean media player property like SeekBackwardsAllowed for example would be helpful. Maybe an event telling you when the cache has completed too.
Also, having a dedicated method would make the API more stable if the internals to seek backwards should change.
Finally, having a NextFrame() method makes me expect there to be a PreviousFrame() method.
Regards,
Mistralys.