Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Framework: Remove client-side document title updates #8831

Merged
merged 7 commits into from
Aug 10, 2018

Conversation

aduth
Copy link
Member

@aduth aduth commented Aug 10, 2018

Closes #3702

This pull request seeks to deprecate the DocumentTitle component and remove its current usage in the editor. This component exists to update the browser tab title on changes to the post's title. With these changes, the title rendered by the server will be used, and will not be manipulated client-side.

Testing instructions:

Verify that there are no title changes which occur client-side.

Ensure the title from the server is correct "Edit Post ‹ Site Title — WordPress"

@aduth aduth added the Framework Issues related to broader framework topics, especially as it relates to javascript label Aug 10, 2018
@danielbachhuber danielbachhuber added this to the 3.6 milestone Aug 10, 2018
@danielbachhuber danielbachhuber added the Backwards Compatibility Issues or PRs that impact backwards compatability label Aug 10, 2018
@danielbachhuber
Copy link
Member

has volunteered to help make necessary revisions to ensure server assigns the correct <title> tag value.

Updated in 417ecf05de7d1734bad950c9d9e36d426844f177

aduth and others added 3 commits August 10, 2018 07:06
It needs to be in a more generic state. Setting the global `$title`
overrides the behavior of `get_admin_page_title()` while still letting
the value be filterable via `admin_title`.
gutenberg.php Outdated
@@ -187,6 +189,16 @@ function gutenberg_init( $return, $post ) {
add_filter( 'screen_options_show_screen', '__return_false' );
add_filter( 'admin_body_class', 'gutenberg_add_admin_body_class' );

$post_type_object = get_post_type_object( $post_type );
/**
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be /*, not /**

Important note: Multi-line comments must not begin with /** (double asterisk) as the parser might mistake it for a DocBlock. Use /* (single asterisk) instead.

https://make.wordpress.org/core/handbook/best-practices/inline-documentation-standards/php/#5-2-multi-line-comments

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated in 2667bf4

@danielbachhuber
Copy link
Member

@aduth I added assertions for the deprecation warnings (66c454d) but they fail locally. Any ideas on the problem?

@danielbachhuber danielbachhuber self-requested a review August 10, 2018 14:31
@danielbachhuber
Copy link
Member

Failure now is:

> phpcs
sh: phpcs: not found
Script phpcs handling the lint event returned with error code 127

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backwards Compatibility Issues or PRs that impact backwards compatability Framework Issues related to broader framework topics, especially as it relates to javascript
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants