Base tag support issues #3978

Closed
johnbender opened this Issue Apr 6, 2012 · 6 comments

Comments

Projects
None yet
4 participants
@johnbender
Contributor

johnbender commented Apr 6, 2012

Information available in the pull request comments:

#3273 (comment)

@ghost ghost assigned jblas Apr 6, 2012

@jaspermdegroot

This comment has been minimized.

Show comment Hide comment
@jaspermdegroot

jaspermdegroot May 26, 2012

Member

@johnbender @jblas

See ticket #4456 which includes a possible solution. Can you review that and, if it is something you want to move on with, close this issue? Thanks!

Member

jaspermdegroot commented May 26, 2012

@johnbender @jblas

See ticket #4456 which includes a possible solution. Can you review that and, if it is something you want to move on with, close this issue? Thanks!

@johnbender

This comment has been minimized.

Show comment Hide comment
@johnbender

johnbender Aug 13, 2012

Contributor

Update here:

I've created a branch that allows for the disabling of the base rewrite as a first step toward the broader solution of allowing the linked documents to define their own base.

Demo: http://jquerymobile.com/branches/basetag/
Build: http://jquerymobile.com/branches/basetag/js/

Testing is required.

Contributor

johnbender commented Aug 13, 2012

Update here:

I've created a branch that allows for the disabling of the base rewrite as a first step toward the broader solution of allowing the linked documents to define their own base.

Demo: http://jquerymobile.com/branches/basetag/
Build: http://jquerymobile.com/branches/basetag/js/

Testing is required.

@ghost ghost assigned johnbender Sep 18, 2012

@toddparker

This comment has been minimized.

Show comment Hide comment
@toddparker

toddparker Dec 6, 2012

Contributor

@johnbender - Is this still on your radar for 1.3?

Contributor

toddparker commented Dec 6, 2012

@johnbender - Is this still on your radar for 1.3?

@johnbender

This comment has been minimized.

Show comment Hide comment
@johnbender

johnbender Apr 2, 2013

Contributor

The branch has been updated, and it's ready to merge. I think we need to just pull it in and live with the change for a bit before 1.4

I want to get this in before starting in on the container refactor.

Contributor

johnbender commented Apr 2, 2013

The branch has been updated, and it's ready to merge. I think we need to just pull it in and live with the change for a bit before 1.4

I want to get this in before starting in on the container refactor.

@jaspermdegroot

This comment has been minimized.

Show comment Hide comment
@jaspermdegroot

jaspermdegroot Apr 5, 2013

Member

I set milestone 1.3.2. If feel it's safe we can cherry-pick it for that release, otherwise wait until 1.4.

Member

jaspermdegroot commented Apr 5, 2013

I set milestone 1.3.2. If feel it's safe we can cherry-pick it for that release, otherwise wait until 1.4.

@jaspermdegroot

This comment has been minimized.

Show comment Hide comment
@jaspermdegroot

jaspermdegroot Jul 18, 2013

Member

The branch has been merged in master. This will land in 1.4. Closing as fixed.

Member

jaspermdegroot commented Jul 18, 2013

The branch has been merged in master. This will land in 1.4. Closing as fixed.

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