Skip to content
This repository has been archived by the owner on Jul 12, 2024. It is now read-only.

Update wordpress monorepo #2929

Merged
merged 13 commits into from
Oct 23, 2019
Merged

Update wordpress monorepo #2929

merged 13 commits into from
Oct 23, 2019

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 18, 2019

This PR contains the following updates:

Package Type Update Change
@wordpress/browserslist-config devDependencies minor 2.4.0 -> 2.6.0
@wordpress/components dependencies minor 8.0.0 -> 8.3.1
@wordpress/compose dependencies minor 3.3.0 -> 3.7.1
@wordpress/custom-templated-path-webpack-plugin devDependencies minor 1.3.0 -> 1.5.0
@wordpress/data dependencies minor 4.5.0 -> 4.9.1
@wordpress/date dependencies minor 3.3.0 -> 3.5.0
@wordpress/element dependencies minor 2.4.0 -> 2.8.1
@wordpress/hooks dependencies minor 2.3.0 -> 2.6.0
@wordpress/html-entities dependencies minor 2.3.0 -> 2.5.0
@wordpress/i18n dependencies minor 3.4.0 -> 3.6.1
@wordpress/jest-preset-default devDependencies minor 4.1.0 -> 4.3.0
@wordpress/keycodes dependencies minor 2.3.0 -> 2.6.1
@wordpress/notices dependencies minor 1.5.0 -> 1.8.1
@wordpress/scripts dependencies minor 3.2.1 -> 3.4.0
@wordpress/url dependencies minor 2.6.0 -> 2.8.0
@wordpress/viewport dependencies minor 2.4.0 -> 2.8.1

Release Notes

WordPress/gutenberg

v2.6.0

Compare Source

v2.5.0

Compare Source


Renovate configuration

📅 Schedule: "before 3am on wednesday" (UTC).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot. View repository job log here.

@renovate renovate bot force-pushed the renovate/wordpress-monorepo branch 4 times, most recently from 10b4d76 to be58c1e Compare September 30, 2019 18:55
@renovate renovate bot changed the title Update wordpress monorepo chore(deps): update wordpress monorepo Sep 30, 2019
@renovate renovate bot changed the title chore(deps): update wordpress monorepo Update wordpress monorepo Oct 1, 2019
@renovate renovate bot force-pushed the renovate/wordpress-monorepo branch 2 times, most recently from da8050b to cedbb96 Compare October 7, 2019 18:03
@renovate
Copy link
Contributor Author

renovate bot commented Oct 7, 2019

PR has been edited

👷 This PR has received other commits, so Renovate will stop updating it to avoid conflicts or other problems. If you wish to abandon your changes and have Renovate start over you may click the "rebase" checkbox in the PR body/description.

Copy link
Collaborator

@psealock psealock left a comment

Choose a reason for hiding this comment

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

Hey @justinshreve, I found an issue with the Compare button styles.

Do you think we need to review how we theme and style these buttons across the app?

client/header/activity-panel/activity-card/style.scss Outdated Show resolved Hide resolved
client/analytics/report/style.scss Outdated Show resolved Hide resolved
@justinshreve
Copy link
Collaborator

Do you think we need to review how we theme and style these buttons across the app?

I think it might be worth a more thorough review of how the PostCSS / colors are injected by Gutenberg, so we can make sure we are doing the right thing. The update here seemed to handle them differently from past versions.

It might also be worth a review of our usage to make sure we are using the correct button type in the correct places (primary / pink or default / gray).

I think the updated CSS I just pushed should style everything correctly now, and would allow us to unblock the version update.

@justinshreve justinshreve self-assigned this Oct 9, 2019
psealock
psealock previously approved these changes Oct 11, 2019
Copy link
Collaborator

@psealock psealock left a comment

Choose a reason for hiding this comment

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

I think the updated CSS I just pushed should style everything correctly now, and would allow us to unblock the version update.

yes, its looking good to me. Thanks for seeing this one through @justinshreve 🚢

@justinshreve
Copy link
Collaborator

Unfortunately I found another bug that needs fixing when testing parts of the application:

When selecting a custom date using the date range filter, selecting a calendar day entry or using the navigation arrows immediately closes the date picker. This does not happen on master.

@justinshreve
Copy link
Collaborator

@jeffstieler I didn't quite get this one all the way through last week. Do you mind adopting it and checking out the date picker bug?

@jeffstieler jeffstieler self-assigned this Oct 14, 2019
@nerrad
Copy link
Contributor

nerrad commented Oct 16, 2019

The datepicker issue should be fixed with a2fd4ce. @jeffstieler had narrowed it down to it being an issue between react-dates triggering a blur event on the mouseup event when clicking the month navigation arrows (originating in the react-dates DayPickerNavigation component) which in turn triggered a focus change. This in turn triggered the close of the Dropdown due to this code:

https://github.com/WordPress/gutenberg/blob/master/packages/components/src/dropdown/index.js#L48-L66

Jeff found this pull which fixed a similar issue happening in Gutenberg core. However, the fix there didn't quite work exactly the same in our case. I'm still not sure why doing the same thing wouldn't work here, but I did eventually realize that we could hook in on the onBlur event in the wrapping div to catch the blur bubbling up and restore focus before it got to the wrapping components.

My testing seemed to indicate all is working okay but could use additional eyes and a round of testing to verify.

@jeffstieler
Copy link
Contributor

@nerrad thanks for that fix! 🙌 I had gotten close, but was definitely missing the onBlur piece.

In testing it seems that the dropdown modal no longer closes when clicking outside, so I'll try to restore that functionality.

@jeffstieler
Copy link
Contributor

jeffstieler commented Oct 16, 2019

I think I've got a solution for the <DateRange> focus issue. This will need a review. 😄

Copy link
Collaborator

@psealock psealock left a comment

Choose a reason for hiding this comment

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

This is testing well for me, besides the keyboard aspect noted below. Nice work getting to this point.

The keyboard navigation issue deserves some attention and hopefully there is a solution.

<div
className="woocommerce-calendar__react-dates"
ref={ this.nodeRef }
onBlur={ partial( this.keepFocusInside, CONTAINER_DIV ) }
Copy link
Collaborator

Choose a reason for hiding this comment

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

Keyboard navigation doesn't let you tab past the first arrow 😭 . I'm not sure how to distinguish a blur event via keyboard navigation from blur event via mouse. Here is a suggestion for setting a flag 🤷‍♀

In any case, until an upstream change happens to react-dates, I think this is an acceptable tradeoff considering the inputs are accessible.

Copy link
Contributor

Choose a reason for hiding this comment

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

Keyboard navigation should be fixed with d03971b.

The one questionable bit is the addition of a losesFocusTo prop to DateRange. It allows the tabbing to continue past the calendar grid and into the comparison period selector.

Copy link
Collaborator

@psealock psealock left a comment

Choose a reason for hiding this comment

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

Nice one Jeff, I never knew about event.relatedTarget!

I agree the added prop losesFocusTo isn't ideal. In theory, this is temporary code though.

In any case, this is testing well with the keyboard. Just a comment about a leftover console.log.

return;
}

console.log( 'looks like a mouseUp() blur', e );
Copy link
Collaborator

Choose a reason for hiding this comment

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

Left a console.log in here

Copy link
Contributor

Choose a reason for hiding this comment

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

Fixed in 5e06c5a.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants