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

Reinvestigate page-follow #103

Closed
bmuenzenmeyer opened this issue Feb 28, 2015 · 4 comments
Closed

Reinvestigate page-follow #103

bmuenzenmeyer opened this issue Feb 28, 2015 · 4 comments

Comments

@bmuenzenmeyer
Copy link
Member

Resurrect #86 and get this working some day

@dmolsen
Copy link
Member

dmolsen commented Mar 1, 2015

BrowserSync?

@bmuenzenmeyer
Copy link
Member Author

That's what I integrated for a moment but the iframe nab messaging was not
keeping up. I think it's possible but I didn't want it holding up a minor
rev. I should put back into a branch for experimentation.

On Sunday, March 1, 2015, Dave Olsen notifications@github.com wrote:

BrowserSync http://www.browsersync.io?


Reply to this email directly or view it on GitHub
#103 (comment)
.

@ivanmayes
Copy link
Contributor

Just FYI, browsersync hit 2.0 and now has a seperate UI for syncing devices, getting error reporting in one place, etc. I've used it with a fork of patternlab and can sync devices to a page via the UI History Panel, but the Patternlab nav still doesn't trigger it. Will take some time at some point to find the event its listening for and maybe we can just trigger that event when the ui changes.

@bmuenzenmeyer
Copy link
Member Author

That's exactly where I got and then stopped. I'm hoping the fix is simple,
only subtle. Thanks for the info on the new 2.0

On Mon, Mar 2, 2015 at 8:23 AM, Ivan Mayes notifications@github.com wrote:

Just FYI, browsersync hit 2.0 and now has a seperate UI for syncing
devices, getting error reporting in one place, etc. I've used it with a
fork of patternlab and can sync devices to a page via the UI History Panel,
but the Patternlab nav still doesn't trigger it. Will take some time at
some point to find the event its listening for and maybe we can just
trigger that event when the ui changes.


Reply to this email directly or view it on GitHub
#103 (comment)
.

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

No branches or pull requests

3 participants