Linking to your options page

Linking directly to
chrome-extension://yourextensionid/youroptionspage.html
will be a bad user experience. Linking directly to
chrome://extensions?options=yourextensionid
isn't advisable either, as Chrome may change the embedding URL in the future.

Messaging APIs

Sizing

The embedded dialogue should automatically determine its own size based on the
options page content. However, the dialogue may not find a good size for some
types of options pages. This problem is most common for options pages that
adjust their size based on window size.

If this is an issue, provide fixed minimum dimensions for the options page to
ensure that the dialogue will find an appropriate size.

Migrating from old options pages

At least until Chrome 40 is stable, you should specify both
the options_uiand the options_page
fields.

Older versions of Chrome will only recognize options_page, and
only open in tabs. Chrome 40 and onwards prefer to use the
options_ui field if it's specified.

The options_ui manifest field and embedded extension options
were introduced in Chrome 40. Prior to these changes, options pages were always
displayed in new tabs and were declared using the options_page
field:

Chrome will continue to support the options_page manifest field,
but new and existing extensions should use the options_ui to
ensure that their options pages are displayed as intended.

If you specify both, Chrome 40 and onwards will ignore the value of
options_page.

In a future version of Chrome, any extension which specifies
options_page will change to match the options_ui
behavior - most importantly, they will always be embedded in
chrome://extensions - so migrate as soon as possible.