Using extend inside a ruleset argument for a mixin

[wjohnsto]

I'm using LESS v2.5.3.

I am trying to extend an element rule inside a ruleset in a mixin as follows:

h1 {
    font-size: 3em;
}

.hero {
    & > .hero-title {
        font-size: 1.5em;

        .phablet({
            &:extend(h1);
        });
    }
}

The .phablet mixin is a mixin that does a min-width media query for phablets. Based on my limited knowledge from reading #1048 it seems like this should work (the font-size should be set to 3em on .phablets. The less compiles fine, but nothing is output, so the font-size remains at 1.5em. Am I doing something wrong?

EDIT: Note this is a somewhat contrived example. In my own code h1s have a bunch of media queries associated with them, and what I would like to do is use the .phablet mixin to reset .hero-title to use those media queries.

[SomMeri]

The :extend inside @media directive is scoped only to rulesets written inside that directive. E.g. this:

h1 { font-size: 3em; }
@media print {
    div-phablet {
      &:extend(h1);
    }
}

compiles into (live example):

h1 {
  font-size: 3em;
}

Example without media:

h1 {  font-size: 3em; }
div-phablet {
  &:extend(h1);
}

compiles into (live example)

h1, div-phablet {
  font-size: 3em;
}

If your .phablet mixin looks somewhat like this, then the extend does not hit h1 because extend is located inside the @media directive. When I comment @media away, extend works. I remember this being discussed in some other issue, but I am not sure which one nor how the discussion ended up (e.g. whether it is bug or feature).

[seven-phases-max]

It's #2095 (pointing to #1165).

As for "no error": hmm, I can't test it with lessc right now, but should not it generate a warning in current versions?

UPD: updated after my mistake, sorry.

[woble]

This does not look like a valid syntax to me to begin with.

.phablet({
    &:extend(h1);
});

[SomMeri]

@woble He defined detached ruleset in a mixin parameter. It works and is just shorter equivalent for:

@detached: {
    &:extend(h1);
};
.phablet(@detached);

[wjohnsto]

@SomMeri This is unfortunate news :(. Luckily there are other ways to accomplish what I need.