When exporting/importing a block display from V2 to V3, if it had the "Exposed Filters in block" option => bug in V3

Not sure it is a bug because it is really an edge case, but it still can save time and headaches to someone, so posting here for the record.

I had a back-Office View (made with Views 2) consisting in a default display and a block display (same settings as the default Display).
This view is used to display a searchable list of articles, so it has exposed filters. I used to check the option that allow to put the exposed filters in a separate block (because I used other modules that needed that)

Then, because I'm a lazy person) like you ;-), I decided to export/import this view to use it on another site that uses Views 3.
Everything turned right except one thing : i couldn't see anymore the expodes filters on the block display (only in the default display), even using the display preview when editing the view.

So @DeFr helped me on that after hours of playing with the view and found that if you import a view in views 3 with :
$handler->display->display_options['exposed_block'] = TRUE;
then this setting is stored in the database view definition (event exported by features), and you will never be able to modify it via the UI.

So deleting this line in code is the only way to get your exposed filters back.

Maybe this can be fixed or not, so i'll let the bug quad decide what to do with this issue